summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/stackcollapse.py
diff options
context:
space:
mode:
authorNamhyung Kim <namhyung@kernel.org>2025-11-06 11:00:23 -0800
committerNamhyung Kim <namhyung@kernel.org>2025-11-06 17:29:16 -0800
commit6bd89ae7d14788ba15e25289479addcb98e7dc26 (patch)
treeffbf7d3cba38ab6825789b4cf718aae4744335cd /tools/perf/scripts/python/stackcollapse.py
parent4df43709370cc18e9b09aa8049a6ab1f780af77e (diff)
downloadlinux-6bd89ae7d14788ba15e25289479addcb98e7dc26.tar.gz
linux-6bd89ae7d14788ba15e25289479addcb98e7dc26.zip
perf record: Make sure to update build-ID cache
Recent change on enabling --buildid-mmap by default brought an issue with build-id handling. With build-ID in MMAP2 records, we don't need to save the build-ID table in the header of a perf data file. But the actual file contents still need to be cached in the debug directory for annotation etc. Split the build-ID header processing and caching and make sure perf record to save hit DSOs in the build-ID cache by moving perf_session__cache_build_ids() to the end of the record__ finish_output(). Reviewed-by: Ian Rogers <irogers@google.com> Signed-off-by: Namhyung Kim <namhyung@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions