Introduction and Consideration of Temporal Partitioning in Avionics With Open Source Eco-System
summary
Defines concrete ARINC 653 requirements for avionics partitioning and shows gaps in current open source stacks, proposing a hypervisor-based architecture using Xen or KVM with Linux guests and musl/glibc libraries. Demonstrates deterministic two‑tier scheduling with a 10 ms major time frame example: three partitions each 3 ms, and per‑partition processes like IMU 1 ms / GPS 2 ms using rate‑monotonic scheduling. Notes a priority numbering mismatch (ARINC 653 uses 1–239) and reports active contributions to Linux/Aerospace working groups and musl test suites.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:06ARINC 653 and IMA
- 4:01ARINC 653 standard
- 10:03Open source gaps
- 12:34Temporal partitioning
- 18:27Gaps analysis
- 20:40Boeing’s open source
- 22:11Q&A
related talks
41mAn Essential Relationship between Real-time and Resource Partitioning
36mStatic Partitioning with Xen, LinuxRT, & Zephyr: A Concrete End-to-end Example
46mBuilding Mixed Criticality Linux Systems with the Jailhouse Hypervisor
16mTuning Linux for Embedded Space Applications
29mSecure and Dynamic Hardware Partitioning Management on Heterogeneous SoC
40mApplication and Challenges of Using GenAVB/TSN Software Stack for Industrial...
20mThe Application of RISC-V Extensions to Automotive Zonal Controllers
51mAdventures in (Simulated) Asymmetric Scheduling