[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <175078758996.337518.10407598236638254580.b4-ty@kernel.org>
Date: Tue, 24 Jun 2025 10:53:09 -0700
From: Namhyung Kim <namhyung@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...hat.com>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Tianyou Li <tianyou.li@...el.com>
Cc: Mark Rutland <mark.rutland@....com>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>, Ian Rogers <irogers@...gle.com>,
Adrian Hunter <adrian.hunter@...el.com>,
Kan Liang <kan.liang@...ux.intel.com>, wangyang.guo@...el.com,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] Read perf data file header from the file user
specified with -i option for perf script flamegraph
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
Powered by blists - more mailing lists