Simple KernelCI Labs with Labgrid
summary
Hardware control stack Labgrid drives ~150 ARM boards via YAML-configured resources (serial, USB fastboot, network, GPIO) and layered Python drivers; a 200-line prototype pulls daily KernelCI builds, flashes kernels over USB/fastboot, runs the same regression tests against a Mainline baseline, and reports results to kcidb. A quick run of an early-batch pipe latency test on a BeagleBone-class board shows a measurable latency decrease (around ~5.4 ms in the initial run), proof-of-concept works end-to-end.
AI-written summary · about
chapters (9)
- 0:00Introduction to Labgrid
- 2:11Labgrid architecture and layers
- 4:59KernelCI Labs goals
- 7:10Demo with BeagleBone
- 8:15Submitting results discussion
- 11:52Reporting regressions
- 13:15Automating performance detection
- 14:42Standardizing kernel artifacts
- 16:50Q&A and closing
related talks
41mPowering Up: Lab Automation With Labgrid and CI
39mQuickly Test Your Kernel with GitLab CI
40mOne year into the new KernelCI
33mMerging an existing framework into KernelCI
20m"GKernelCI v.2 new features and KernelCI compatibility"- 20mGKernelCI v.2 new features and KernelCI compatibility
38mQuality Beyond Kernelci.Org in Upstream Linux for TI SoCs
51mIntroducing the “Lab in a Box” Concept