From: TAKANO Mitsuhiro <takano32@gmail.com>
To: linux-perf-users@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>
Cc: Ian Rogers <irogers@google.com>,
Mark Rutland <mark.rutland@arm.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Jiri Olsa <jolsa@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
linux-kernel@vger.kernel.org,
TAKANO Mitsuhiro <takano32@gmail.com>
Subject: [PATCH 0/3] perf vendor events: Fix misspellings in event and metric descriptions
Date: Fri, 20 Nov 2026 17:58:37 +0000 [thread overview]
Message-ID: <20261120175840.1274637-1-takano32@gmail.com> (raw)
The PMU event descriptions shipped in the JSON tables under
tools/perf/pmu-events/arch/ are printed by `perf list` (BriefDescription)
and `perf list -v` (PublicDescription) as they are written, and the metric
descriptions in the metrics JSON files are printed by `perf list metric`.
A number of them carry misspelled words, so the misspellings reach the
user. This series fixes the first batch of them, which a spell-check pass
over the power8, power9 and power10 tables and over the Intel and AMD
tables turned up.
The three patches are split by vendor because that is the convention for
the subject prefix in this tree. Of the 989 commits that touch
tools/perf/pmu-events/arch/ as of 65e4fd942f72, `perf vendor events
intel:` has 391, `amd:` 37, `powerpc:` 8, `arm64:` 83, `s390:` 18 and
`riscv:` 13. No commit with a vendor prefix touches another vendor's
tables.
The arm64 tables have misspellings of the same kind ("misprediciton" in
the ampere tables, "executed.This" in the cortex-a55 tables); the s390
and riscv tables contain none of the words fixed here. More remain in the
tables this series swept and in others -- "conjection" and "banwidth" in
the Intel uncore tables, "pumpfor" in power8, to name a few -- and those
are left for follow-up patches.
Each patch touches description strings only, and each was checked by
regenerating the tables with
jevents.py <arch> all tools/perf/pmu-events/arch out.c out-str.c
and diffing the result against the one generated from the parent commit:
every event name and event code is unchanged, and the misspellings are
gone from the generated string table. out-str.c shrinks or stays the same
size, because some corrected descriptions become identical to descriptions
already stored for other models, and the amd fix swaps a word for another
of the same length:
powerpc 13 files, 55 lines changed out-str.c -393 bytes
intel 5 files, 5 lines changed out-str.c -477 bytes
amd 1 file, 1 line changed out-str.c size unchanged
65 PublicDescription values in power8/other.json end in "42"; the trailing
"42" is not a misspelling, so it is left alone. The word "ibufffully"
in that file is left unchanged as well: the BriefDescription of the same
event ends with "ibuff", so the boundary is clear, but whether a space or
a full stop belongs after it is not.
Written with Hermes Agent, an LLM assistant: it found the words and wrote
these changelogs and this cover note; the author reviewed every change and
ran the generator as described above.
Signed-off-by: TAKANO Mitsuhiro <takano32@gmail.com>
TAKANO Mitsuhiro (3):
perf vendor events powerpc: Fix misspellings in the power tables
perf vendor events intel: Fix misspellings in the Intel model tables
perf vendor events amd: Fix a misspelling in the amdzen3 table
.../arch/powerpc/power10/metrics.json | 8 ++--
.../pmu-events/arch/powerpc/power8/cache.json | 2 +-
.../arch/powerpc/power8/memory.json | 2 +-
.../arch/powerpc/power8/metrics.json | 8 ++--
.../pmu-events/arch/powerpc/power8/other.json | 38 +++++++++----------
.../arch/powerpc/power8/pipeline.json | 4 +-
.../pmu-events/arch/powerpc/power8/pmc.json | 4 +-
.../pmu-events/arch/powerpc/power9/cache.json | 2 +-
.../arch/powerpc/power9/frontend.json | 2 +-
.../arch/powerpc/power9/marked.json | 4 +-
.../arch/powerpc/power9/metrics.json | 6 +--
.../pmu-events/arch/powerpc/power9/other.json | 28 +++++++-------
.../arch/powerpc/power9/translation.json | 2 +-
.../pmu-events/arch/x86/amdzen3/branch.json | 2 +-
.../arch/x86/nehalemep/pipeline.json | 2 +-
.../arch/x86/nehalemex/pipeline.json | 2 +-
.../arch/x86/sierraforest/srf-metrics.json | 2 +-
.../arch/x86/westmereep-dp/pipeline.json | 2 +-
.../arch/x86/westmereep-sp/pipeline.json | 2 +-
19 files changed, 61 insertions(+), 61 deletions(-)
base-commit: 65e4fd942f72a9dba0e4e257290c4fa1aa756854
--
2.53.0
next reply other threads:[~2026-11-20 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-20 17:58 TAKANO Mitsuhiro [this message]
2026-11-20 17:58 ` [PATCH 1/3] perf vendor events powerpc: Fix misspellings in the power tables TAKANO Mitsuhiro
2026-11-20 18:01 ` sashiko-bot
2026-11-20 17:58 ` [PATCH 2/3] perf vendor events intel: Fix misspellings in the Intel model tables TAKANO Mitsuhiro
2026-11-20 18:01 ` sashiko-bot
2026-11-20 17:58 ` [PATCH 3/3] perf vendor events amd: Fix a misspelling in the amdzen3 table TAKANO Mitsuhiro
2026-11-20 18:00 ` sashiko-bot
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=20261120175840.1274637-1-takano32@gmail.com \
--to=takano32@gmail.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--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