All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: James Clark <james.clark@linaro.org>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-perf-users@vger.kernel.org, Gabriel Marin <gmx@google.com>
Subject: Re: [PATCH] perf inject: Keep build-ID data if no option is used
Date: Thu, 8 Jan 2026 15:57:28 -0800	[thread overview]
Message-ID: <aWBEaNVsoizw4Aax@google.com> (raw)
In-Reply-To: <CAP-5=fXShAb9Ez-j64fY8c_XDpRUp33Z1Z75jS9=+UaTKa68HQ@mail.gmail.com>

Hi Ian,

On Wed, Dec 17, 2025 at 10:57:01AM -0800, Ian Rogers wrote:
> On Wed, Dec 17, 2025 at 10:39 AM Namhyung Kim <namhyung@kernel.org> wrote:
> >
> > The keep_feat() determines which header features will be kept or
> > discarded.  Usually perf inject will add build-IDs based on -b, -B or
> > other related options.  But it lose build-ID when none of those options
> > are used.  This is meaningful only when --buildid-mmap is not used.
> >
> > The following example shows the impact of this change.
> >
> >   $ perf record --no-buildid-mmap true
> >   [ perf record: Woken up 1 times to write data ]
> >   [ perf record: Captured and wrote 0.037 MB perf.data (5 samples) ]
> >
> >   $ perf inject -i perf.data -o perf.data.inject
> >
> >   $ perf buildid-list -i perf.data
> >   08cccc2a9388d5247ccb3e864f3063b975b0a15d /usr/lib/x86_64-linux-gnu/ld-linux-x86-64.so.2
> >   fd5c4d5673256cd6bda51725dba048dabb0f854e [kernel.kallsyms]
> >   97a36ce1140071be5c36b147fa0bed173e05a602 [vdso]
> >
> >   $ perf buildid-list -i perf.data.inject
> >   97a36ce1140071be5c36b147fa0bed173e05a602 [vdso]
> >
> > With this change, perf.data.inject would show the same list (of course,
> > you need to run perf inject again).
> >
> > Reported-by: Gabriel Marin <gmx@google.com>
> > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> 
> Reviewed-by: Ian Rogers <irogers@google.com>

Thanks for the review!

Arnaldo, any chance you can pick this up soon?

Thanks,
Namhyung


  reply	other threads:[~2026-01-08 23:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-17 18:39 [PATCH] perf inject: Keep build-ID data if no option is used Namhyung Kim
2025-12-17 18:57 ` Ian Rogers
2026-01-08 23:57   ` Namhyung Kim [this message]
2026-01-13 20:16     ` Arnaldo Carvalho de Melo

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=aWBEaNVsoizw4Aax@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=gmx@google.com \
    --cc=irogers@google.com \
    --cc=james.clark@linaro.org \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@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 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.