NVIDIA's Approach for Achieving ASIL B Qualified Linux
summary
NVIDIA claims a practical path to ISO 26262 ASIL B for Linux by treating Linux as an SEooC and isolating safety code with context-specific page tables that create MMU-enforced memory partitioning. Implementation instruments per-function context switches (not per-thread), dimensions safety memory pools, and performs call‑chain analysis to capture nested dependencies; overhead concentrates in initialization and increases memory use and page-table-swap CPU work. Prototype runs on ARM64, uses a hypervisor backing, requires modest kernel MM changes, and an automotive assessor expects it to meet ASIL B.
AI-written summary · about
chapters (7)
- 0:00Introduction to safety with Linux
- 5:41Why safety matters now
- 10:38Challenges of Linux for safety
- 17:41Linux kernel spatial interference problem
- 23:17NVIDIA’s context-based approach
- 35:17Safety boundary and certification
- 37:04Q&A and future plans
related talks
41mIs Linux Kernel Development Good Enough to Make Your Life Depend on It?
42mDecoding Safe(ty) Linux Architectural Approaches for Critical Systems
31mSafe Software for Autonomous Mobility With Modern C++
33mAdopting Linux on BMW - The Long Road to Integrate Linux as Mainline Platform
42mZephyr Functional Safety BOF
26mHow to Qualify a Safe Linux Distribution in Cars
19mQualification of the C and C++ Standard Libraries for Safety-critical Applications
22mOS-A SEE Explained