|
|
Log in / Subscribe / Register

Linux in mixed-criticality systems

Linux in mixed-criticality systems

Posted Dec 13, 2018 18:39 UTC (Thu) by nopsled (guest, #129072)
Parent article: Linux in mixed-criticality systems

It would also be nice to have some infrastructure for proper Priority Inheritance in the kernel as part of this, apart from the already present rt_mutex, the last time I ever heard about that from the Realtime effort, associating the interrupt ID with the kernel thread was described to be the hard part. The seL4 developers recently published a paper on using the scheduling context as capabilities as part of their time protection effort, and being able to transfer the clients time slice to the server to achieve that (supporting cases where a server could become unscheduled completely if it happens to have no scCaps, and then transitioning back from that passive state on reception of scCaps from a client). IDK how that would work under Linux, and if trying to map them to file descriptors would be an acceptable approach. Not only can this be useful for system calls, it will also be useful for userspace itself, or for IPC systems that want to bill clients for method calls they make, or charge someone's request over another's. Binder currently uses nice values to emulate this, which is at best, a hack.


to post comments

Linux in mixed-criticality systems

Posted Dec 13, 2018 20:55 UTC (Thu) by smurf (subscriber, #17840) [Link]

Hmm. I fail to see what PI has to do with this article. Presumably, a hard-RT system that runs on Jailhouse will unequivocally own any hardware it controls, and will not talk to Linux on any mission-critical code path. So why should the Linux kernel's ability, or not, to do "proper Priority Inheritance" matter here?

Linux in mixed-criticality systems

Posted Dec 14, 2018 19:41 UTC (Fri) by glenn (subscriber, #102223) [Link]

The SCHED_DEADLINE developers have been pushing forward on a set of WIP patches from Peter Zijlstra to revamp PI to use a bandwidth-server-based approach to PI: https://www.spinics.net/lists/linux-rt-users/msg19573.html

This is good for mixed-criticality systems, because it helps isolates potential side-effects of PI to the threads that share resources. Independent threads are generally isolated from the effects of bandwidth-server-based PI employed by other threads (this is not the case with simple PI). This helps realize the "freedom from interference" requirement of some safety standards (e.g., the automotive ISO-26262 standard).

Folks have used real-time Linux in mission-critical applications. SpaceX has been open about their heavy use of Linux on their rockets: https://lwn.net/Articles/540368/


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds