All of lore.kernel.org
 help / color / mirror / Atom feed
From: Beau Belgrave <beaub@linux.microsoft.com>
To: namhyung@kernel.org, jolsa@kernel.org, acme@kernel.org,
	peterz@infradead.org, mingo@kernel.org
Cc: linux-trace-devel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Perf MMAP records differ from /proc/[X]/maps when chroot is used
Date: Wed, 1 Jun 2022 11:04:04 -0700	[thread overview]
Message-ID: <20220601180404.GA2029@kbox> (raw)

I noticed a related conversation that occurred in the past here:
https://lore.kernel.org/lkml/20220202070828.143303-1-namhyung@kernel.org/

I hit this same issue, however, during debugging I noticed that when
chroot is used the full path including the chroot are in /proc/[X]/maps.
The perf MMAP records only give the relative path within the chroot.

This causes different views of a process when combining mmaps that existed
before perf_event_open() via /proc/[X]/maps and observed mmaps within the
perf_event_open() ring buffer.

I would like to know if this is how mmap records are wanted to be represented
long term via perf? It would be great if these mmap records aligned with how
/proc/[X]/maps are represented so chroot usage becomes (mostly) seamless.

Thanks,
-Beau

                 reply	other threads:[~2022-06-01 18:04 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220601180404.GA2029@kbox \
    --to=beaub@linux.microsoft.com \
    --cc=acme@kernel.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.