From: "Mi, Dapeng" <dapeng1.mi@linux.intel.com>
To: Ian Rogers <irogers@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Kan Liang <kan.liang@linux.intel.com>,
James Clark <james.clark@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Yoshihiro Furudera <fj5100bi@fujitsu.com>,
Howard Chu <howardchu95@gmail.com>,
Thomas Falcon <thomas.falcon@intel.com>,
Andi Kleen <ak@linux.intel.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/3] Improve event groups for topdown, add X event modifier
Date: Tue, 26 Aug 2025 10:30:10 +0800 [thread overview]
Message-ID: <3f481d00-2c9f-45a5-807b-037930903b1c@linux.intel.com> (raw)
In-Reply-To: <20250825211204.2784695-1-irogers@google.com>
On 8/26/2025 5:12 AM, Ian Rogers wrote:
> In:
> https://lore.kernel.org/lkml/20250822082233.1850417-1-dapeng1.mi@linux.intel.com/#t
> Dapeng Mi and Xudong Hao reported that Intel topdown events have
> issues with parsing when events are duplicated. While some of that is
> intended, things could be better. These patches:
>
> 1) give error messages specific to topdown event grouping constraints,
> 2) fail groups if non-leaders fail to open (this appears to be old tech debt),
> 3) adds an 'X' event modifier to allow events to opt-out of being regrouped.
>
> The 'X' modifier should also give a means to side-step future issues
> in parse_events__sort_events_and_fix_groups should they come up.
>
> Ian Rogers (3):
> perf evsel: Give warning for broken Intel topdown event grouping
> perf stat: Don't skip failing group events
> perf parse-events: Add 'X' modifier to exclude an event from being
> regrouped
>
> tools/perf/Documentation/perf-list.txt | 1 +
> tools/perf/arch/x86/util/evsel.c | 62 ++++++++++++++++++++++++--
> tools/perf/builtin-stat.c | 48 +++++++++-----------
> tools/perf/util/evsel.c | 7 ++-
> tools/perf/util/evsel.h | 3 +-
> tools/perf/util/parse-events.c | 5 ++-
> tools/perf/util/parse-events.h | 1 +
> tools/perf/util/parse-events.l | 5 ++-
> 8 files changed, 94 insertions(+), 38 deletions(-)
The whole patch-set looks good to me.
Reviewed-by: Dapeng Mi <dapeng1.mi@linux.intel.com>
Tested the patches on Intel Sapphire Rapids and Panther Lake, all results
are expected.
Tested-by: Dapeng Mi <dapeng1.mi@linux.intel.com>
Test results on Sapphire Rapids.
1. sudo ./perf stat -e slots,slots -a sleep 1
WARNING: events were regrouped to match PMUs
Error:
Topdown slots event can only be group leader in '{slots,slots}'.
2. sudo ./perf stat -e slots,slots:X -a sleep 1
Performance counter stats for 'system wide':
55,734,800,895 slots
(49.99%)
57,217,900,875 slots:X
(50.01%)
1.009697323 seconds time elapsed
3. sudo ./perf stat -e slots,topdown-fe-bound,topdown-fe-bound -a sleep 1
WARNING: events were regrouped to match PMUs
Error:
Perf metric event 'topdown-fe-bound' is duplicated in the same group (only
one event is allowed) in '{slots,topdown-fe-bound,topdown-fe-bound}'.
4. Perf stats test
sudo ./perf test 100
100: perf stat tests : Ok
Test results on Panther Lake.
1. sudo ./perf stat -e slots,slots -a sleep 1
WARNING: events were regrouped to match PMUs
Error:
Topdown slots event can only be group leader in
'{cpu_core/slots/,cpu_core/slots/}'.
2. sudo ./perf stat -e slots,slots:X -a sleep 1
Performance counter stats for 'system wide':
1,592,899,478 cpu_core/slots/
(49.98%)
1,682,298,980 cpu_core/slots/X
(50.02%)
1.002821768 seconds time elapsed
3. sudo ./perf stat -e slots,topdown-fe-bound,topdown-fe-bound -a sleep 1
WARNING: events were regrouped to match PMUs
Error:
Perf metric event 'cpu_core/topdown-fe-bound/' is duplicated in the same
group (only one event is allowed) in
'{cpu_core/slots/,cpu_core/topdown-fe-bound/,cpu_core/topdown-fe-bound/},cpu_atom/topdown-fe-bound/,cpu_atom/topdown-fe-bound/'.
4. sudo ./perf test 99
99: perf stat tests : Ok
next prev parent reply other threads:[~2025-08-26 2:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 21:12 Ian Rogers
2025-08-25 21:12 ` [PATCH v1 1/3] perf evsel: Give warning for broken Intel topdown event grouping Ian Rogers
2025-08-25 21:12 ` [PATCH v1 2/3] perf stat: Don't skip failing group events Ian Rogers
2025-08-25 21:12 ` [PATCH v1 3/3] perf parse-events: Add 'X' modifier to exclude an event from being regrouped Ian Rogers
2025-10-17 7:25 ` Mi, Dapeng
2025-10-17 16:59 ` Ian Rogers
2025-08-26 2:30 ` Mi, Dapeng [this message]
2025-09-12 18:48 ` [PATCH v1 0/3] Improve event groups for topdown, add X event modifier 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=3f481d00-2c9f-45a5-807b-037930903b1c@linux.intel.com \
--to=dapeng1.mi@linux.intel.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=fj5100bi@fujitsu.com \
--cc=gregkh@linuxfoundation.org \
--cc=howardchu95@gmail.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--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=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=thomas.falcon@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®