perf build IDs
summary
New perf flow stores build ids in the kernel memory map events so perf record skips the slow post-processing and no longer needs perf archive; perf report or perf buildid cache then download binaries via debuginfod to populate the debug cache on the reporting host. Kernel and tooling patches landed weeks ago and target Linux 5.11, so the claim is implemented and working in recent releases; remaining work adds detection when kernel build-id parsing fails so users can fallback to user‑space reads.
AI-written summary · about
chapters (14)
- 0:00Intro
- 1:25Current workflow
- 3:47New workflow overview
- 5:34No perf archive step
- 7:00What is build ID
- 8:43Why build ID
- 11:05Debug Cache
- 11:54Memory Map
- 12:21Build ID Map
- 13:34Debug Info Demon
- 14:50perfrecord
- 16:04debuginfodemon
- 16:42status
- 18:35QA
related talks
45mPerformance lab. The power of the perf tool!
37mAdvanced Performance Profiling Using Perf Tools
24mlibperf: library for perf events monitoring
45mPerf tools updates and beyond
29mPerf Support in Xen
31mFantastic tracepoints and where to find them
43mAdvanced System Profiling Tracing and Trace Analysis with Perfetto
16mPerf feature improvements in RISCV