Virtualization & Mixed-Criticality: Running ASIL-D RTOS and QM Linux POSIX on Shared Silicon
Configuring Type-1 embedded hypervisors (BlackBerry QNX, PikeOS, OpenSynergy) to isolate safety-critical real-time domains from infotainment stacks.
Consolidating multiple domains onto a single HPC silicon die introduces significant mixed-criticality safety challenges. If an unprivileged Android Automotive OS infotainment application crashes or encounters a memory leak, it must never impact the ASIL-D braking or steering controller.
Type-1 bare-metal hypervisors enforce strict hardware virtualization: • CPU Core Affinity: Dedicating physical CPU cores exclusively to safety partitions. • Hardware Memory Virtualization (Stage 2 MMU): Preventing virtual machines from reading or writing unauthorized physical RAM pages. • Interrupt and I/O Virtualization (IOMMU): Isolating PCIe and Ethernet hardware peripherals, guaranteeing Freedom from Interference (FFI) per ISO 26262 Part 6.