EAS Unit Testing
summary
C-based LTP tests validate concrete EAS and scheduler behaviors by enabling ftrace and parsing it with a custom trace parser; merged into an AOSP LTP fork. Implemented checks include EAS task placement, sched boost vs. utilization, schedutil governor responsiveness and wakeup counts, CFS bandwidth correctness, deadline runtime checks and RT FIFO/RR ordering. Tested on Pixel 3 and HiKey960: several failures show migration latency >100 ms, small tasks running on big cores, schedutil ~70 ms, and SCHED deadline latency ≈300 µs. Thresholds are configurable; aim is upstream and VTS compliance.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:42common sources of customization
- 1:44typical validation
- 2:22some issues observed
- 4:56rt-tests.git
- 7:13LISA
- 8:52small standalone EAS tests
- 9:43tests currently implemented
- 13:06current test results - pixel 3 wlaosp and 4.9
- 17:09future plans
related talks
48mAn Unbiased Look at the Energy Aware Scheduler (EAS)
18mScheduler Tracing With ftrace + eBPF
33mLKFT experiences and plans
30mHow to get realistic c-state latency and residency?
24mEnergy model accuracy
40mLatency hints for CFS task
28mLatency hints for CFS task
41mKeeping up with LTS: Linux Kernel Functional Testing (LKFT) on Devices