From: Namhyung Kim <namhyung@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Tianyou Li <tianyou.li@intel.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
wangyang.guo@intel.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] tools/perf: Add --exclude-buildids option to perf archive command
Date: Fri, 27 Jun 2025 11:53:07 -0700 [thread overview]
Message-ID: <175105038774.2492671.5711747632083820597.b4-ty@kernel.org> (raw)
In-Reply-To: <20250625161509.2599646-1-tianyou.li@intel.com>
On Thu, 26 Jun 2025 00:14:01 +0800, Tianyou Li wrote:
> When make a perf archive, it may contains the binaries that user did not want to ship with,
> add --exclude-buildids option to specify a file which contains the buildids need to be
> excluded. The file can be generated from command:
>
> perf buildid-list -i perf.data --with-hits | grep -v "^ " > exclude-buildids.txt
>
> Then remove the lines from the exclude-buildids.txt for buildids should be included.
>
> [...]
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
next prev parent reply other threads:[~2025-06-27 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aFrzSpvzzWeHdyJ5 () google ! com>
2025-06-25 16:14 ` Tianyou Li
2025-06-27 18:53 ` Namhyung Kim [this message]
2025-06-30 1:36 ` Li, Tianyou
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=175105038774.2492671.5711747632083820597.b4-ty@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tianyou.li@intel.com \
--cc=wangyang.guo@intel.com \
/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®