From: Nazar Kazakov <nazar.kazakov@codethink.co.uk>
To: 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>, Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Ben Dooks <ben.dooks@codethink.co.uk>,
Nazar Kazakov <nazar.kazakov@codethink.co.uk>
Subject: [PATCH] perf jevents: make events order more deterministic
Date: Mon, 6 Jul 2026 18:56:24 +0100 [thread overview]
Message-ID: <20260706175624.692736-1-nazar.kazakov@codethink.co.uk> (raw)
Some of the events have the same name, but differing descriptions. This
leads to a non-deterministic sorting order, so fix by adding the
description field to the order.
Signed-off-by: Nazar Kazakov <nazar.kazakov@codethink.co.uk>
---
tools/perf/pmu-events/metric.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/perf/pmu-events/metric.py b/tools/perf/pmu-events/metric.py
index a91ccb5977f0..b3ab78a0ecb2 100644
--- a/tools/perf/pmu-events/metric.py
+++ b/tools/perf/pmu-events/metric.py
@@ -623,7 +623,7 @@ class Metric:
def __lt__(self, other):
"""Sort order."""
- return self.name < other.name
+ return self.name < other.name or self.description < other.description
def AddToMetricGroup(self, group):
"""Callback used when being added to a MetricGroup."""
--
2.54.0
next reply other threads:[~2026-07-06 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 17:56 Nazar Kazakov [this message]
2026-07-06 18:01 ` [PATCH] perf jevents: make events order more deterministic sashiko-bot
2026-07-06 18:04 ` Ian Rogers
2026-07-06 18:22 ` Nazar Kazakov
2026-07-06 18:48 ` Ian Rogers
2026-07-06 19:08 ` Nazar Kazakov
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=20260706175624.692736-1-nazar.kazakov@codethink.co.uk \
--to=nazar.kazakov@codethink.co.uk \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ben.dooks@codethink.co.uk \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jolsa@kernel.org \
--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 \
/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