Maintaining a Real Time Stable Kernel
summary
Maintains the PREEMPT_RT stable trees by merging stable releases one-by-one (examples: 4.9 → 4.14 → 4.16, with long‑term 3.18 kept only if needed), incrementing the -RT version and tagging any merge that produces conflicts so the exact bad merge is traceable. Uses a rebased branch to produce clean quilt/patch queues and runs quick smoke tests after each conflict resolution, then a full test sweep before release. Uses git cherry to collect RT-only commits and tracks backports in shared docs. Local_lock annotates per‑CPU critical sections.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:30Upstream Stable Releases
- 2:18Real Time Stable Releases
- 5:06Real Time Stable Process
- 11:46Merging Mainline Stable into RT Stable
- 15:30The Rebase Branch
- 19:59Priority Inversion
- 21:19Priority Inheritance is Hard
- 24:28Disabling Preemption
- 29:23Disabling Interrupts
- 31:39Dealing with Conflicts (Easy)
- 36:32Dealing with No Conflicts (hard)
- 39:04Backporting RT patches
- 44:28git cherry
related talks
38mThe Status of the Preempt-RT Patch
47mReal-Time Linux: What Is Next?
42mBoF: Realtime Linux
50mInside the RT Patch
53mPREEMPT_RT - How Not to Break It.
40mRT Linux in Safety-Critical Systems: The Potential and the Challenges
01h 08mRT Linux in Safety Critical Systems: the potential and the challenges
33mQ&A about Preempt RT