Xen in Safety-Critical Systems
summary
Xen claims a concrete path toward safety certification: hypervisor core drops below 50,000 lines of code (goal <30k), Dom0 becomes optional so guests can boot Dom0‑less, and static features (static memory, CPU pools, shared memory and event channels) land upstream. Interrupt forwarding costs about 1,900 instructions in measured cases and cache coloring yields ~3 µs interrupt latency on the board. Tooling includes cppcheck, eclare.it scans, GitLab CI and XTF for tests.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:26What Is Safety
- 1:32Why Exam Matters for Safety
- 2:20Mixed Criticality
- 7:42What Is Real-Time in Software
- 9:23Interrupts
- 12:37Mpu Support
- 16:22Split the Cache
- 18:10Why Does It Matter for Safety
- 20:21Static Memory
- 22:32Static Even Channels
- 23:09Static Cpu Pools
- 27:03K-Config
- 31:54Improving K Config
related talks
50mXen Project's Progress Toward Safety Certification
30mXen Functional Safety - an Update
48mXen and the Art of Embedded Systems Virtualization
38mBuilding Hard Real-Time Linux Systems with Xenomai
33mNext Generation Xen Architecture for Automotive
49mSteering Xenomai into the Real-Time Linux Future
29mPerformance Optimization on Xen-based Android Device
36mStatic Partitioning with Xen, LinuxRT, & Zephyr: A Concrete End-to-end Example