Checking your work: Linux kernel testing and CI
summary
Kselftest stores suites as simple make entries with test_progs and test_gen_progs, builds an install directory and emits a runnable test runner that produces ktap output. Many suites work but several have unmet external dependencies: BPF needs a very recent clang/LLVM and RCU torture currently lives outside default targets and needs porting and kernel builds with specific CPU/RAM setups. A checkdeps script exists to analyze missing libraries and cross‑compile needs so CI can provision what tests actually require.
AI-written summary · about
chapters (8)
- 0:00Introduction to talk
- 1:02What is Kselftest
- 4:09Evolution of Kselftest
- 8:04Dependencies and configurations
- 10:51Future of Kselftest features
- 13:59Common configuration format
- 16:29Philosophical questions
- 17:58Conclusion and Q&A
related talks
34mLinux Kernel Testing: Providing Better Results to the Upstream Community
30mKernel Testing with KUnit: Bridging the Gap- 34mLinux Kernel Testing: Providing Better Results to the Upstream Community
23mExperiences and lessons we learned using kselftest and pote
50mTips for Writing Good Tests for Linux
16mKselftests augmented: running kernelspace tests from userspace
44mKUnit - Unit Testing for the Linux Kernel
38mQuality Beyond Kernelci.Org in Upstream Linux for TI SoCs