From: Namhyung Kim <namhyung@kernel.org>
To: Tianyou Li <tianyou.li@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
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, pan.deng@intel.com,
zhiguo.zhou@intel.com, tim.c.chen@intel.com,
tim.c.chen@linux.intel.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Minor improvements for perf script flamegraph
Date: Mon, 9 Jun 2025 18:19:51 -0700 [thread overview]
Message-ID: <aEeIN_u4KpLZXDBx@google.com> (raw)
In-Reply-To: <20250603071048.180674-1-tianyou.li@intel.com>
Hello,
On Tue, Jun 03, 2025 at 03:10:48PM +0800, Tianyou Li wrote:
> When processing the perf data file generated with multiple events,
> the flamegraph script will count all the events regardless of
> different event names. 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 patch tries to add a -e option to specify the event name that
> the flamegraph will be generated accordingly. If the -e option omitted,
> the behavior remains unchanged. If the -i option specified, the header
> information will be read from that file.
Looks like two separate changes. Can you please split them?
Thanks,
Namhyung
>
> Signed-off-by: Tianyou Li <tianyou.li@intel.com>
> Reviewed-by: Pan Deng <pan.deng@intel.com>
> Reviewed-by: Zhiguo Zhou <zhiguo.zhou@intel.com>
> Reviewed-by: Wangyang Guo <wangyang.guo@intel.com>
> Reviewed-by: Tim Chen <tim.c.chen@linux.intel.com>
> ---
> tools/perf/scripts/python/flamegraph.py | 21 +++++++++++++++++++--
> 1 file changed, 19 insertions(+), 2 deletions(-)
>
> diff --git a/tools/perf/scripts/python/flamegraph.py b/tools/perf/scripts/python/flamegraph.py
> index cf7ce8229a..eb78b93925 100755
> --- a/tools/perf/scripts/python/flamegraph.py
> +++ b/tools/perf/scripts/python/flamegraph.py
> @@ -94,6 +94,11 @@ class FlameGraphCLI:
> return child
>
> def process_event(self, event):
> + # ignore events where the event name does not match
> + # the one specified by the user
> + if self.args.event_name and event.get("ev_name") != self.args.event_name:
> + return
> +
> pid = event.get("sample", {}).get("pid", 0)
> # event["dso"] sometimes contains /usr/lib/debug/lib/modules/*/vmlinux
> # for user-space processes; let's use pid for kernel or user-space distinction
> @@ -123,8 +128,15 @@ class FlameGraphCLI:
> return ""
>
> try:
> - output = subprocess.check_output(["perf", "report", "--header-only"])
> - return output.decode("utf-8")
> + if self.args.input:
> + output = subprocess.check_output(["perf", "script", "--header-only", "-i", self.args.input])
> + else:
> + output = subprocess.check_output(["perf", "report", "--header-only"])
> +
> + result = output.decode("utf-8")
> + if self.args.event_name:
> + result += "\nFocused event: " + self.args.event_name
> + return result
> except Exception as err: # pylint: disable=broad-except
> print("Error reading report header: {}".format(err), file=sys.stderr)
> return ""
> @@ -235,6 +247,11 @@ if __name__ == "__main__":
> default=False,
> action="store_true",
> help="allow unprompted downloading of HTML template")
> + parser.add_argument("-e", "--event",
> + default="",
> + dest="event_name",
> + type=str,
> + help="specify the event to generate flamegraph for")
>
> cli_args = parser.parse_args()
> cli = FlameGraphCLI(cli_args)
> --
> 2.43.5
>
next prev parent reply other threads:[~2025-06-10 1:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 7:10 [PATCH] Minor improvements for perf script flamegraph Tianyou Li
2025-06-10 1:19 ` Namhyung Kim [this message]
2025-06-10 3:20 ` 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=aEeIN_u4KpLZXDBx@google.com \
--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=pan.deng@intel.com \
--cc=peterz@infradead.org \
--cc=tianyou.li@intel.com \
--cc=tim.c.chen@intel.com \
--cc=tim.c.chen@linux.intel.com \
--cc=wangyang.guo@intel.com \
--cc=zhiguo.zhou@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 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.