Bringing Existing Open-Source Code into MISRA Compliance
summary
Work on Zephyr and Xen targets MISRA compliance for selected x86_64 and arm64 configurations, funded partly by AMD, and produces documented deviations in the Xen repo; tooling and tailoring cut violations dramatically (about 97% reduction in one case) by encoding safe exceptions to MISRA rule 10.1 and wrapping obscure bit tricks in named macros, while compiler qualification, CI gating of patches and a Kconfig/preprocessor compromise keep builds reproducible and prevent regressions.
AI-written summary · about
chapters (7)
- 0:00MISRA introduction
- 2:59Open-source in safety systems
- 12:54Adopted vs existing code
- 16:51Tailoring MISRA guidelines
- 19:24Xen hypervisor case study
- 34:06Lessons from compliance
- 41:10Q&A
related talks
51mMISRA C and C++ in OSS: Yes, We Can!
46mSafety-Certifying Open Source Software: The Case of the Xen Hypervisor
45mSafety Certifying an Open Source Project: The Example of Xen
40mBOF: Open Source Projects in Safety Critical Applications
32mDeveloping Open Source for Safety and Security
19mXen Project 2024 Weather Report
40mContributing to Zephyr vs (Linux and U-boot)
44mThe Road to Safety Certification: How the Xen Project is Making Progress within the Auto Industry