微软开源ThreadX
Microsoft open-sources ThreadX

原始链接: https://www.theregister.com/2023/11/28/microsoft_opens_sources_threadx/

周一早上,研究人员使用安装在纽约布鲁克海文国家实验室大型强子对撞机内的专用摄像机发现了一个极其罕见的涉及夸克的事件:在原子粉碎机内同时看到了成对的“上”和“下”夸克。 称为“美丽背景事件”——因为当亚原子粒子在粒子碰撞内快速移动时,当夸克对彼此经过时,在它们存在的短暂时间内用彩色光照亮内部背景风景,以便夸克碰撞——它们看起来很美丽,或者 对人眼来说,“美丽”——“美丽背景”在物理学家中闻名,因为在巨大的地下实验室内观看令人兴奋的场景,同时以音频配乐的形式大声播放真人视频记录。 2023 年 5 月 12 日,世界上最大的粒子对撞机发生了第十次碰撞,其方式引起了其创造者的注意。 加州大学伯克利分校能源部运营主任、物理学家马克·S·麦克诺(Mark S. McNaught)将大型强子对撞机内正在进行的实验称为“美丽背景”,因为这是科学内部的美,而不是流行文化内部的美。 在实验室内,由物理学研究教授黛安·戈尔丁(Diane Goldin)领导的团队正在运行计算机程序,其目的是模拟夸克在质子-质子碰撞中配对时的样子。 与此同时,城里竞争对手大学实验室内的一个竞争团队也在同时努力改进和调整对撞机内的高能电子枪技术,包括测试和校准阴极轨。 在网上同时报道的一项进展中,物理学家克里斯托夫·珀尔(Christoph Perl)正在瑞士日内瓦欧洲核子研究组织(CERN)内的费米实验室隔壁的费米实验室内进行记录,该加速器隧道的设计类似于大型同步回旋加速器,其目的类似于在更大的同步回旋加速器内进行记录。 兄弟对撞机位于美国新泽西州边界对面。 周五下午,科学家们终于很幸运,进入了超导磁体实验室内的两台对撞机,以保护证人,这两个对撞机分别是较小的兄弟质子同步回旋加速器对撞机和位于地下的较大的姐妹质子-反质子同步回旋加速器对撞机 加速器内的洞穴系统

这些评论与讨论没有直接关系,但似乎反映了对合并或转发的不同文章或提交内容的担忧和意见,以及出版物做出的写作风格或编辑决定。 尽管欢迎意见和批评,但重要的是它们与当前主题保持相关性,并且不要分散对正在讨论的要点的注意力。 在这种情况下,有关“并行线程标准”的评论似乎意味着与当前主题的混淆,这可能会降低整个对话的清晰度和相关性。 此外,提及“公认的出版标准”的评论似乎暗示了对出版商编辑选择的不满或批评,尽管承认此类惯例和期望通常存在并有其目的。 总体而言,这些言论中隐含的建议似乎有利于指导围绕当前主题进行更清晰、更有针对性的对话。
相关文章

原文

Microsoft is open sourcing the realtime operating system that it acquired with Express Logic, donating it to the Eclipse Foundation.

The vendor has made its ThreadX RTOS, and the Azure RTOS development suite that includes it, open source. The company has contributed Azure RTOS to the stewardship of the Eclipse Foundation, where it will be known as Eclipse ThreadX and available under the permissive MIT licence.

Although there are many Real-time OSes – RTOS for short – out there, you generally don't hear much about them. You may never have heard of ThreadX, but there's a fairly good chance that you unwittingly have several copies lying around or even running right now.

There are more famous RTOSes, such as Wind River's VxWorks: it's running on Mars, inside NASA's Perseverance Rover for example. Blackberry's QNX RTOS, which we called the money-making part of the business, has been in the spotlight twice: once as the basis for RIM's Blackberry X fondleslab and smartphone range, but back in the 1990s for the amazing QNX single-floppy demo disk.

ThreadX was quite pervasive, though. Microsoft claims 12 billion devices run it, and you might own some of them. For a while it powered Intel's on-chip Management Engine. It is also the firmware that controls every Raspberry Pi bigger than the Pi Pico. On the Pi 1, 2 and 3, it's the file on your Pi's SD card called bootcode.bin; in the Pi 4 and 400, it's called start*.elf. Even though it's on GitHub and included in Debian, it's a proprietary "blob" (Binary Large OBject). It's a metaphorical sealed black box which doesn't even contain Arm code: instead, it runs on the Pi's VideoCore GPU. This is the primary device, the part that boots up the Pi and controls its hardware: the Arm cores are slave devices to the VideoCore GPU.

This, incidentally, is why Xen only runs on the Pi 4 and later: they were the first versions where the Arm cores had their own interrupt controller, and even so, it took some work. We have read that in the Pi 5, it's in EEPROM and does even less, meaning that the Arm cores have more control, as this Reg comment bears out.

As soon as this innocent little OS turned 21 in 2019, Microsoft grabbed it, acquiring ThreadX owners Express Logic and rebranding the poor thing as Azure RTOS, which hasn't done any favours for its brand awareness. The purchase came soon after AWS took over stewardship of FreeRTOS, and some observers, such as this commenter on Reddit, claim that the deal was a response to Amazon's move. After the purchase, original developer William Lamie left, starting a new company which sells a "fifth-generation" RTOS with POSIX-compatible threads, called PX5OS.

Even so, ThreadX is a tested and established product; some parts even have TÜV Functional Safety (FuSa) certification, such as the STM32 version [PDF]. That kind of thing is powerfully attractive to some customers.

At this point, only the current version is on GitHub, and we don't see any trace of a VideoCore version. Although the GPU drivers have long been open source, the firmware never was, and attempts to write an independent FOSS version were never completed, for reasons explained on the project page. Now, there is at least some hope that the Raspberry Pi Foundation might be able to get permission to release the source code for its version. As of last year, the foundation had sold over 46 million of the things, and if the whole software stack were open source, that would make them even more appealing for a lot of people. ®

联系我们 contact @ memedata.com