Linux perf inserts multiple probes on line of code with a macro
I am using perf to insert probes on a line of code that’s a macro. For example in the CPython implementation I would like to insert a record to be made every time the GIL is unlocked on line 164:
Can perf record associate build IDs with PIDs instead of paths to avoid overwriting when paths are identical?
When using perf record with the perf record -a
option on a host machine to profile system-wide, I encounter an issue where executables in different containers have the same file paths. This results in build IDs overwriting each other since perf record identifies ELF binaries using these paths. Is it feasible to modify perf record to use process IDs (PIDs) as keys for storing build IDs to prevent this issue? Or are there any alternative solutions to distinguish build IDs in such scenarios?
linux perf tool impact on application execution time
We have a simple tool runtime_probe that performs some hardware checks.