[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM9d7cjiCT7C=WHd9EmPRRRQY=1aq8-NAGgRcZPWz-s=7Js3mw@mail.gmail.com>
Date: Wed, 7 Feb 2024 21:26:09 -0800
From: Namhyung Kim <namhyung@...nel.org>
To: Adrian Hunter <adrian.hunter@...el.com>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>, Jiri Olsa <jolsa@...nel.org>, Ian Rogers <irogers@...gle.com>,
Like Xu <like.xu.linux@...il.com>, linux-kernel@...r.kernel.org,
linux-perf-users@...r.kernel.org
Subject: Re: [PATCH V2 0/2] perf symbols: Slightly improve module file
executable section mappings
Hi Adrian,
On Tue, Feb 6, 2024 at 5:05 AM Adrian Hunter <adrian.hunter@...el.com> wrote:
>
> 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 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
Acked-by: Namhyung Kim <namhyung@...nel.org>
Thanks,
Namhyung
>
> 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
Powered by blists - more mailing lists