About The Need to Power Instrument The Linux Kernel
Talkat Embedded Linux Conference + OpenIoT Summit North America 2017 · on Thursday, 2017-02-23· at 09:00· Broadway III/IV·
summary
Linux already exposes Ftrace power events that log regulator, clock, CPU freq/idle and GPIO transitions; combining those timestamps with a per-device power table (proposal: device tree power profiles) lets software estimate platform watts without external probes. Prototype tools parse traces to produce min/avg/max power, time-in-states, transition counts and plots, enable CI regressions, and could feed closed‑loop governors or visualizers like KernelShark. Missing pieces are a maintained power database and polished post‑processing/plotting tools; a proof‑of‑concept parser exists.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:37Agenda
- 1:15Why Power Management Instrumentation Is Needed
- 3:51Why Do We Need Power Instrumentation
- 4:45Debug Power Leaks
- 7:08Power Modeling
- 8:56Enabling Closed Loop Power Management Policies
- 12:33Power Analysis Tool
- 15:10Collect Power Events with F Trace
- 16:12Impact on Performance
- 35:57Offline Processing of the Trace
related talks
37mPower Measurement and Attribution for Processes and Hardware Devices in the Linux...
42mPower Measurement and Attribution in Kernel for Embedded System Processes- 42mPower Measurement and Attribution in Kernel for Embedded System Processes
55mLinux Kernel Debug And Profiling Tools
42mHow Much Is Tracing? Measuring the Overhead Caused by the Tracing Infrastructure
55mRecent Advances in Linux Tracing
27mMeasuring Carbon Footprint of Personal Computing
35mLinux Tracing updates