perf tools: Random fixes for DWARF unwind
Status from this message: Thanks, applied to perf-tools-next.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | perf genelf: Set ELF program header addresses properlytools/ | +3 | 1 reply | |
| 2/3 | perf unwind-libdw: Handle JIT-generated DSOs properlytools/ | +17 | 2 replies | |
| 3/3 | perf unwind-libunwind: Fix base address for .eh_frametools/ | +1 | 1 reply |
Reviews trailers per patch
2 of 3 patches have a Reviewed-by or Acked-by.
| Patch | Ian Rogers |
|---|---|
| 1/3 | R-b |
| 2/3 | |
| 3/3 | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/3] perf tools: Random fixes for DWARF unwind
Hello,
I've found a couple of issues on the unwind code while I'm playing with the JIT-dump code for the CPython. The code assumes normal DSOs mapped from the beginning of the file and aligned to the page size. But it's not true for the JIT-dumped DSOs which are generated for each function.
Depending on the JIT implementation, the code address and accompanied ELF info (like ELF file headers and unwind info) can be overlapped to adjacent (JIT-dumped) DSOs. So it should take more care when it calculates the mapping address for the DSO.
It seems these changes need to go to the stable trees but they are changed a lot since then so I'm not sure.
Thanks,
Namhyung
Namhyung Kim (3):
perf genelf: Set ELF program header addresses properly perf unwind-libdw: Handle JIT-generated DSOs properly perf unwind-libunwind: Fix base address for .eh_frame
tools/perf/util/genelf.c | 6 +++--- tools/perf/util/unwind-libdw.c | 21 +++++++++++++++++---- tools/perf/util/unwind-libunwind-local.c | 2 +- 3 files changed, 21 insertions(+), 8 deletions(-)
Signature · 1 line
2.43.0.472.g3155946c3a-goog