Defining and maintaining requirements in the Linux...
summary
ELISA Architecture WG drafts a requirements template and applies it to the tracing subsystem, finding and fixing a redundant flag and documenting a non‑atomic read that can corrupt events rather than changing behavior. A three‑part upstream submission includes a guideline, a devmem specification and test code converted to KUnit; maintainer pushback leads to dropping the guideline and adopting minimal bulleted specs for traceability. A sidecar CI/hash approach flags stale specs; sampling 10% of a file finds two serious bugs.
AI-written summary · about
chapters (10)
- 0:00Introduction and context
- 1:04Requirements template overview
- 3:14Kernel documentation importance
- 5:25Tracing subsystem trials
- 7:08Dev me documentation feedback
- 13:43Open discussion on next steps
- 20:41Maintaining formal documentation
- 25:16Formalism and maintainer concerns
- 31:34Proposed next actions
- 36:47Closing remarks and Q&A
related talks
53mDocumenting the Design of the Linux Kernel
41mCross Industry Demands and Collaboration Opportunities
01h 01mTraceability and Automation Examples With Basil
27mContinuous Compliance: Agile Practices for Software Compliance
25mContinuous compliance with Rust in automotive software
26mHow to Qualify a Safe Linux Distribution in Cars
19mQualification of the C and C++ Standard Libraries for Safety-critical Applications
31mLiterate Tracing