How to introduce KUnit to physical...
summary
Describes adding KUnit to physical DRM drivers by converting existing driver tests and running them on donated GPUs; team converts many CASE-OF tests, lands them integrated into DRM suite and IGT, and exercises real hardware (finds an architecture-endian failure and a regression in domain-list value handling). Shows concrete options for testing static functions: export test case instead of internal symbols, include tests in-module or build a standalone test module, and notes KUnit currently triggers on module load.
AI-written summary · about
chapters (9)
- 0:00Introduction and project overview
- 1:47Starting KUnit integration process
- 3:55Testing static functions with KUnit
- 6:03Exporting test cases for static functions
- 7:04Community discussion on testing approaches
- 10:15Technical challenges and solutions
- 13:07Standalone vs driver-integrated tests
- 15:24Bugs found and testing outcomes
- 17:52Learning from case of test conversion
related talks
28mTesting Drivers with KUnit (Does hardware have to be hard?)
30mKernel Testing with KUnit: Bridging the Gap
44mKUnit - Unit Testing for the Linux Kernel
45mKUnit: Past, Present, and Future
16mHow do we make KUnit work for us?- 45m"KUnit: Past, Present, and Future"
24mKUnit Testing Insufficiencies
28mKVM-unit-tests: When "KVM" Doesn't Mean KVM