How to Qualify a Safe Linux Distribution in Cars
summary
RHIVOS is an OSTree variant of RHEL with a rebuilt RT kernel and an explicit claim to meet ISO 26262 ASIL B; requirements come from API manpages and are broken into testable low‑level requirements, with automated diffs and MR workflows when manpages change. Testing runs in Auto Toolchain CI, TMT and CKI pipelines, uses code‑coverage per API aiming for 100% coverage for complex APIs, and stores bi‑directional traceability in Polarion for requirements and test assets.
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:21Agenda
- 0:56Overview of Red Hat In-Vehicle Operating System
- 3:00Automotive Safety Integrity Levels
- 4:58Red Hat In-Vehicle Operating System Test Strategy
- 7:16Requirements Testing
- 9:07Importance of Code Coverage in Functional Safety Systems
- 9:54Code Coverage Workflows
- 10:40Freedom From Interference
- 11:37DFA: Dependent Failure Analysis
- 12:21FMEA: Inductive Analysis
- 13:45Process Aspect
- 15:49Workflow of deriving Requirements and Assumptions/Conditions of Use
- 16:57Detection and Handling impact of Manpage changes on requirements
- 17:43Requirements Changes Management-Generic Workflow
- 18:37Traceability
related talks
42mEnabling Linux in Safety-Critical Applications
19mAutomotive Linux for RISC-V
28mLinux in Cars! CentOS AutoSD, SDVs, and more
01h 00mAutoSD: A Linux Development and Prototyping Framework for the Automotive Community
46mRAFIA – A Roadmap for Certifying Open Source for Use in Safety-Relevant Systems
50mLinux You Can Drive My Car
42mBoF: Safety + Open Source Software: Where it Started & Where It's Going
33mDeveloping RHEL open source way