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 1/2] Read perf data file header from the file user specified with -i option for perf script flamegraph
Date: Tue, 24 Jun 2025 10:53:09 -0700 [thread overview]
Message-ID: <175078758996.337518.10407598236638254580.b4-ty@kernel.org> (raw)
In-Reply-To: <20250610040536.2390060-1-tianyou.li@intel.com>
On Tue, 10 Jun 2025 12:04:22 +0800, Tianyou Li wrote:
> If specify the perf data file with -i option, the script will try to read the header information
> regardless of the file name specified, instead it will try to access the perf.data. This simple
> patch use the file name from -i option for command perf report --header-only to read the header.
>
>
Applied to perf-tools-next, thanks!
Best regards,
Namhyung
next prev parent reply other threads:[~2025-06-24 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <aEeIN_u4KpLZXDBx () google ! com>
2025-06-10 4:04 ` Tianyou Li
2025-06-10 4:04 ` [PATCH 2/2] Add -e option to focus on the specific event for generating the flamegraph Tianyou Li
2025-06-24 17:53 ` Namhyung Kim [this message]
2025-06-25 15:24 ` [PATCH 1/2] Read perf data file header from the file user specified with -i option for perf script flamegraph 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=175078758996.337518.10407598236638254580.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®