From: TAKANO Mitsuhiro <takano32@gmail.com>
To: linux-perf-users@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>
Cc: Ian Rogers <irogers@google.com>,
John Garry <john.garry@linux.dev>,
James Clark <james.clark@linaro.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Ilkka Koskinen <ilkka@os.amperecomputing.com>,
TAKANO Mitsuhiro <takano32@gmail.com>
Subject: [PATCH] perf vendor events arm64: AmpereOne/AmpereOneX: Fix typos
Date: Sat, 7 Nov 2026 05:17:30 +0000 [thread overview]
Message-ID: <20261107051730.1880691-1-takano32@gmail.com> (raw)
Three distinct words are misspelled in eight description fields in the
AmpereOne and AmpereOneX PMU tables: "Preditable" in BPU_BTB_UPDATE
(AmpereOneX only), "satisified" in LD_FROM_ST_FWD, and "misprediciton"
in the branch_mispredict metric. jevents.py copies the strings into the
generated tables, so perf list prints them and a grep for the correct
spelling misses the entries.
Fix both fields where an entry has them; the metrics entries carry only a
brief description. No event code, metric expression or reported value
changes, and the generated tables are not tracked, so the diff is JSON
only. ISTALL - the other codespell hit here - is the ETM stall-control
bit name, left alone.
Written with Hermes Agent, an LLM assistant. Running jevents.py on this
change produces none of the three words; perf was not rebuilt, so the
perf list output was not checked.
Signed-off-by: TAKANO Mitsuhiro <takano32@gmail.com>
---
.../arch/arm64/ampere/ampereone/core-imp-def.json | 4 ++--
.../pmu-events/arch/arm64/ampere/ampereone/metrics.json | 2 +-
.../arch/arm64/ampere/ampereonex/core-imp-def.json | 8 ++++----
.../pmu-events/arch/arm64/ampere/ampereonex/metrics.json | 2 +-
4 files changed, 8 insertions(+), 8 deletions(-)
diff --git a/tools/perf/pmu-events/arch/arm64/ampere/ampereone/core-imp-def.json b/tools/perf/pmu-events/arch/arm64/ampere/ampereone/core-imp-def.json
index 879ff21e0b17..5a82a7717060 100644
--- a/tools/perf/pmu-events/arch/arm64/ampere/ampereone/core-imp-def.json
+++ b/tools/perf/pmu-events/arch/arm64/ampere/ampereone/core-imp-def.json
@@ -450,10 +450,10 @@
"BriefDescription": "OFB full cycles"
},
{
- "PublicDescription": "Load satisified from store forwarded data",
+ "PublicDescription": "Load satisfied from store forwarded data",
"EventCode": "0xD605",
"EventName": "LD_FROM_ST_FWD",
- "BriefDescription": "Load satisified from store forwarded data"
+ "BriefDescription": "Load satisfied from store forwarded data"
},
{
"PublicDescription": "L1 prefetcher, load prefetch requests generated",
diff --git a/tools/perf/pmu-events/arch/arm64/ampere/ampereone/metrics.json b/tools/perf/pmu-events/arch/arm64/ampere/ampereone/metrics.json
index 324104438e78..76cdf38b1e58 100644
--- a/tools/perf/pmu-events/arch/arm64/ampere/ampereone/metrics.json
+++ b/tools/perf/pmu-events/arch/arm64/ampere/ampereone/metrics.json
@@ -260,7 +260,7 @@
{
"MetricName": "branch_mispredict",
"MetricExpr": "(BR_MIS_PRED_RETIRED / GPC_FLUSH) * slots_lost_misspeculation_fraction",
- "BriefDescription": "Fraction of slots lost due to branch misprediciton",
+ "BriefDescription": "Fraction of slots lost due to branch misprediction",
"MetricGroup": "TopdownL2",
"ScaleUnit": "1percent of slots"
},
diff --git a/tools/perf/pmu-events/arch/arm64/ampere/ampereonex/core-imp-def.json b/tools/perf/pmu-events/arch/arm64/ampere/ampereonex/core-imp-def.json
index eb5a2208d260..558b13fd7d0d 100644
--- a/tools/perf/pmu-events/arch/arm64/ampere/ampereonex/core-imp-def.json
+++ b/tools/perf/pmu-events/arch/arm64/ampere/ampereonex/core-imp-def.json
@@ -84,10 +84,10 @@
"BriefDescription": "Predictable branch speculatively executed, unpredicted, that mispredict"
},
{
- "PublicDescription": "Preditable branch update the BTB region buffer entry",
+ "PublicDescription": "Predictable branch update the BTB region buffer entry",
"EventCode": "0x11c",
"EventName": "BPU_BTB_UPDATE",
- "BriefDescription": "Preditable branch update the BTB region buffer entry"
+ "BriefDescription": "Predictable branch update the BTB region buffer entry"
},
{
"PublicDescription": "Count predict pipe stalls due to speculative return address predictor full",
@@ -438,10 +438,10 @@
"BriefDescription": "Fill buffer full"
},
{
- "PublicDescription": "Load satisified from store forwarded data",
+ "PublicDescription": "Load satisfied from store forwarded data",
"EventCode": "0xD605",
"EventName": "LD_FROM_ST_FWD",
- "BriefDescription": "Load satisified from store forwarded data"
+ "BriefDescription": "Load satisfied from store forwarded data"
},
{
"PublicDescription": "Store retirement pipe stall",
diff --git a/tools/perf/pmu-events/arch/arm64/ampere/ampereonex/metrics.json b/tools/perf/pmu-events/arch/arm64/ampere/ampereonex/metrics.json
index a29aadc9b2e3..a0dc917b9462 100644
--- a/tools/perf/pmu-events/arch/arm64/ampere/ampereonex/metrics.json
+++ b/tools/perf/pmu-events/arch/arm64/ampere/ampereonex/metrics.json
@@ -260,7 +260,7 @@
{
"MetricName": "branch_mispredict",
"MetricExpr": "(BR_MIS_PRED_RETIRED / GPC_FLUSH) * slots_lost_misspeculation_fraction",
- "BriefDescription": "Fraction of slots lost due to branch misprediciton",
+ "BriefDescription": "Fraction of slots lost due to branch misprediction",
"MetricGroup": "TopdownL2",
"ScaleUnit": "1percent of slots"
},
base-commit: d48723711bae9b8cdc56719c448ba42fef28cbee
--
2.53.0
reply other threads:[~2026-11-07 5:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261107051730.1880691-1-takano32@gmail.com \
--to=takano32@gmail.com \
--cc=acme@kernel.org \
--cc=ilkka@os.amperecomputing.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.garry@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@kernel.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
all inboxes | Powered by JetHome®