Hi

Currently perf does not record module section addresses except for
the .text section. In general that means perf cannot get module section
mappings correct (except for .text) when loading symbols from a kernel
module file. (Note using --kcore does not have this issue)

Here are a couple of patches to help shed light upon and slightly improve
the situation.


Changes in V3:

  Re-base

Changes in V2:

  perf tools: Make it possible to see perf's kernel and module memory mappings
    - add dump to perf report (if no browser) as well as perf script
    - add 'perf --debug kmaps' option also to dump kmaps


Adrian Hunter (2):
      perf tools: Make it possible to see perf's kernel and module memory mappings
      perf symbols: Slightly improve module file executable section mappings

 tools/perf/Documentation/perf.txt |  2 ++
 tools/perf/builtin-report.c       |  2 ++
 tools/perf/builtin-script.c       |  3 ++
 tools/perf/util/debug.c           |  3 ++
 tools/perf/util/debug.h           |  1 +
 tools/perf/util/python.c          |  1 +
 tools/perf/util/session.c         | 11 ++++++
 tools/perf/util/session.h         |  2 ++
 tools/perf/util/symbol-elf.c      | 75 +++++++++++++++++++++++++++++++++++++--
 9 files changed, 98 insertions(+), 2 deletions(-)


Regards
Adrian

On Thu, 8 Feb 2024 10:53:24 +0200, Adrian Hunter wrote:
> Currently perf does not record module section addresses except for
> the .text section. In general that means perf cannot get module section
> mappings correct (except for .text) when loading symbols from a kernel
> module file. (Note using --kcore does not have this issue)
> 
> Here are a couple of patches to help shed light upon and slightly improve
> the situation.
> 
> [...]

Applied to perf-tools-next, thanks!

Best regards,
-- 
Namhyung Kim <namhyung@kernel.org>