linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 0/2] perf symbols: Slightly improve module file executable section mappings
Date: Fri,  2 Feb 2024 13:01:28 +0200	[thread overview]
Message-ID: <20240202110130.3553-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.


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


Regards
Adrian

             reply	other threads:[~2024-02-02 11:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-02 11:01 Adrian Hunter [this message]
2024-02-02 11:01 ` [PATCH 1/2] perf script: Make it possible to see perf's kernel and module memory mappings Adrian Hunter
2024-02-03  1:50   ` Namhyung Kim
     [not found]     ` <CA+JHD91GR=Jry_=Es4m+JnySjMoKrfajW40ZHq+eYFaF9Vsngg@mail.gmail.com>
2024-02-05  7:08       ` Adrian Hunter
2024-02-06  2:21         ` Namhyung Kim
2024-02-02 11:01 ` [PATCH 2/2] perf symbols: Slightly improve module file executable section mappings Adrian Hunter
2024-02-03  1:44   ` Namhyung Kim
2024-02-05  6:58     ` Adrian Hunter
2024-02-06  2:21       ` 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=20240202110130.3553-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).