From: Ian Rogers <irogers@google.com>
To: Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@kernel.org>,
Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
Sandipan Das <sandipan.das@amd.com>,
Chun-Tse Shao <ctshao@google.com>,
John Garry <john.g.garry@oracle.com>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
Nazar Kazakov <nazar.kazakov@codethink.co.uk>
Subject: [PATCH v1 0/3] perf jevents: Deterministic build fix and mypy cleanliness
Date: Mon, 6 Jul 2026 20:40:16 -0700 [thread overview]
Message-ID: <20260707034019.241762-1-irogers@google.com> (raw)
Nazar Kazakov reported non-deterministic builds due to the metrics
being reordered in the jevents.py output. Fix by sorting metrics on
more than just their name.
Checking the code with mypy showed a large range of type warnings. Fix
by largely adding asserts that values aren't None and by adding type
annotations.
Ian Rogers (3):
perf jevents: Add more components to the metric sorting order
perf jevents: Add python type annotations
perf jevents metric: Add python type annotations
tools/perf/pmu-events/jevents.py | 82 +++++++++++++++++++-------------
tools/perf/pmu-events/metric.py | 23 +++++----
2 files changed, 62 insertions(+), 43 deletions(-)
--
2.55.0.795.g602f6c329a-goog
next reply other threads:[~2026-07-07 3:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-07 3:40 Ian Rogers [this message]
2026-07-07 3:40 ` [PATCH v1 1/3] perf jevents: Add more components to the metric sorting order Ian Rogers
2026-07-07 3:58 ` sashiko-bot
2026-07-07 3:40 ` [PATCH v1 2/3] perf jevents: Add python type annotations Ian Rogers
2026-07-07 3:40 ` [PATCH v1 3/3] perf jevents metric: " Ian Rogers
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=20260707034019.241762-1-irogers@google.com \
--to=irogers@google.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ctshao@google.com \
--cc=james.clark@linaro.org \
--cc=john.g.garry@oracle.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=nazar.kazakov@codethink.co.uk \
--cc=peterz@infradead.org \
--cc=sandipan.das@amd.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