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.
