From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, Namhyung Kim <namhyung@kernel.org>,
Ian Rogers <irogers@google.com>,
Like Xu <like.xu.linux@gmail.com>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org
Subject: [PATCH V3 0/2] perf symbols: Slightly improve module file executable section mappings
Date: Thu, 8 Feb 2024 10:53:24 +0200 [thread overview]
Message-ID: <20240208085326.13432-1-adrian.hunter@intel.com> (raw)
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
next reply other threads:[~2024-02-08 8:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 8:53 Adrian Hunter [this message]
2024-02-08 8:53 ` [PATCH V3 1/2] perf tools: Make it possible to see perf's kernel and module memory mappings Adrian Hunter
2024-02-08 8:53 ` [PATCH V3 2/2] perf symbols: Slightly improve module file executable section mappings Adrian Hunter
2024-02-09 22:16 ` [PATCH V3 0/2] " Namhyung Kim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240208085326.13432-1-adrian.hunter@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=like.xu.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).