mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@redhat.com>, Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Andi Kleen <ak@linux.intel.com>, Ian Rogers <irogers@google.com>
Subject: Re: [PATCH 0/4] Handle chroot tasks properly (v2)
Date: Thu, 10 Feb 2022 22:16:59 -0800	[thread overview]
Message-ID: <CAM9d7cikhttPHQ7CXRvNq5mLfoojt-ke_2bKz0T3Z1o+hTFb8A@mail.gmail.com> (raw)
In-Reply-To: <YgVa0/B7MUKRz88C@kernel.org>

Hi Arnaldo,

On Thu, Feb 10, 2022 at 10:35 AM Arnaldo Carvalho de Melo
<acme@kernel.org> wrote:
>
> Em Tue, Feb 01, 2022 at 11:08:24PM -0800, Namhyung Kim escreveu:
> > Hello,
> >
> > I found that perf tools don't work well with tasks in a chroot.  The
> > filenames in MMAP record are from the root directory of the task so
> > it's different than what it sees from outside.
> >
> >  * changes in v2)
> >   - add Jiri's Acked-by
> >   - split stderr setup for objdump
>
> Applied 1/4 to perf/urgent, its already upstream.
>
> The others are bit big for this time, so I've added it to perf/core.

Perfect, thanks for your work!

Namhyung

      reply	other threads:[~2022-02-11  6:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02  7:08 Namhyung Kim
2022-02-02  7:08 ` [PATCH 1/4] perf annotate: Set error stream of objdump process for TUI Namhyung Kim
2022-02-02  7:08 ` [PATCH 2/4] perf tools: Try chroot'ed filename when opening dso/symbol Namhyung Kim
2022-02-02  7:08 ` [PATCH 3/4] perf inject: Try chroot directory when reading build-id Namhyung Kim
2022-02-02  7:08 ` [PATCH 4/4] perf annotate: Try chroot filename for objdump Namhyung Kim
2022-02-10 18:34 ` [PATCH 0/4] Handle chroot tasks properly (v2) Arnaldo Carvalho de Melo
2022-02-11  6:16   ` Namhyung Kim [this message]

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=CAM9d7cikhttPHQ7CXRvNq5mLfoojt-ke_2bKz0T3Z1o+hTFb8A@mail.gmail.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®