All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH 0/3] perf vendor events: Fix misspellings in event and metric descriptions
@ 2026-11-20 17:58 TAKANO Mitsuhiro
  2026-11-20 17:58 ` [PATCH 1/3] perf vendor events powerpc: Fix misspellings in the power tables TAKANO Mitsuhiro
                   ` (2 more replies)
  0 siblings, 3 replies; 7+ messages in thread
From: TAKANO Mitsuhiro @ 2026-11-20 17:58 UTC (permalink / raw)
  To: linux-perf-users, Peter Zijlstra, Ingo Molnar,
	Arnaldo Carvalho de Melo, Namhyung Kim
  Cc: Ian Rogers, Mark Rutland, Alexander Shishkin, Jiri Olsa,
	Adrian Hunter, James Clark, linux-kernel, TAKANO Mitsuhiro

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


^ permalink raw reply	[flat|nested] 7+ messages in thread

* [PATCH 1/3] perf vendor events powerpc: Fix misspellings in the power tables
  2026-11-20 17:58 [PATCH 0/3] perf vendor events: Fix misspellings in event and metric descriptions TAKANO Mitsuhiro
@ 2026-11-20 17:58 ` 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 17:58 ` [PATCH 3/3] perf vendor events amd: Fix a misspelling in the amdzen3 table TAKANO Mitsuhiro
  2 siblings, 1 reply; 7+ messages in thread
From: TAKANO Mitsuhiro @ 2026-11-20 17:58 UTC (permalink / raw)
  To: linux-perf-users, Peter Zijlstra, Ingo Molnar,
	Arnaldo Carvalho de Melo, Namhyung Kim
  Cc: Ian Rogers, Mark Rutland, Alexander Shishkin, Jiri Olsa,
	Adrian Hunter, James Clark, linux-kernel, TAKANO Mitsuhiro

Thirty-two different words are wrong, 69 times in all, in 54 descriptions
of the power8, power9 and power10 tables.  Fifteen of them appear more
than once: "than than" and "thee" eight times each, "exceed" five times,
"cyles", "finshed" and "cant" four times each, "software.Fuzzy" three
times, and "coverted", "repoted", "Fetchs", "whtver", "Micrpartition",
"dmand", "invalidat" and "tread" twice each; the other seventeen appear
once.

62 of the 69 are in BriefDescription fields and seven in PublicDescription
fields, so `perf list` prints those 62 and `perf list -v` prints those
seven.  Eleven of the 62 are metric descriptions, printed by `perf list
metric`.

Sixteen of the 69 are not misspellings: eight are a doubled "than", four
are missing spaces ("touchto" in "touch to L3", and "software.Fuzzy" in
"software. Fuzzy" three times), and four are "cant" without its
apostrophe.

One more description in power8/other.json has a space inside each of two
words ("Group experi enced Non-specu lative I cache miss"); a sibling
description above it spells them "experienced non-speculative", so the two
words are joined as well.  Fifty-five descriptions change in total.

Only the descriptions change.  Regenerating the tables with

  jevents.py powerpc all tools/perf/pmu-events/arch out.c out-str.c

leaves every event name and event code untouched, and the misspellings are
gone from the generated out-str.c, which shrinks by 393 bytes as some
corrected descriptions become identical to ones already stored for other
models.

Signed-off-by: TAKANO Mitsuhiro <takano32@gmail.com>
---
 .../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 +-
 13 files changed, 55 insertions(+), 55 deletions(-)

diff --git a/tools/perf/pmu-events/arch/powerpc/power10/metrics.json b/tools/perf/pmu-events/arch/powerpc/power10/metrics.json
index a36621858ea3..0830eba7769b 100644
--- a/tools/perf/pmu-events/arch/powerpc/power10/metrics.json
+++ b/tools/perf/pmu-events/arch/powerpc/power10/metrics.json
@@ -755,25 +755,25 @@
         "MetricName": "TLBIE_PER_INST"
     },
     {
-        "BriefDescription": "Average number of STCX instructions finshed per completed instruction",
+        "BriefDescription": "Average number of STCX instructions finished per completed instruction",
         "MetricExpr": "PM_STCX_FIN / PM_RUN_INST_CMPL",
         "MetricGroup": "General",
         "MetricName": "STCX_PER_INST"
     },
     {
-        "BriefDescription": "Average number of LARX instructions finshed per completed instruction",
+        "BriefDescription": "Average number of LARX instructions finished per completed instruction",
         "MetricExpr": "PM_LARX_FIN / PM_RUN_INST_CMPL",
         "MetricGroup": "General",
         "MetricName": "LARX_PER_INST"
     },
     {
-        "BriefDescription": "Average number of PTESYNC instructions finshed per completed instruction",
+        "BriefDescription": "Average number of PTESYNC instructions finished per completed instruction",
         "MetricExpr": "PM_PTESYNC_FIN / PM_RUN_INST_CMPL",
         "MetricGroup": "General",
         "MetricName": "PTESYNC_PER_INST"
     },
     {
-        "BriefDescription": "Average number of simple fixed-point instructions finshed in the store unit per completed instruction",
+        "BriefDescription": "Average number of simple fixed-point instructions finished in the store unit per completed instruction",
         "MetricExpr": "PM_FX_LSU_FIN / PM_RUN_INST_CMPL",
         "MetricGroup": "General",
         "MetricName": "FX_PER_INST"
diff --git a/tools/perf/pmu-events/arch/powerpc/power8/cache.json b/tools/perf/pmu-events/arch/powerpc/power8/cache.json
index 05a17084d939..c5907a51b897 100644
--- a/tools/perf/pmu-events/arch/powerpc/power8/cache.json
+++ b/tools/perf/pmu-events/arch/powerpc/power8/cache.json
@@ -128,7 +128,7 @@
   {
     "EventCode": "0x3001a",
     "EventName": "PM_DATA_TABLEWALK_CYC",
-    "BriefDescription": "Tablwalk Cycles (could be 1 or 2 active)",
+    "BriefDescription": "Tablewalk Cycles (could be 1 or 2 active)",
     "PublicDescription": "Data Tablewalk Active"
   },
   {
diff --git a/tools/perf/pmu-events/arch/powerpc/power8/memory.json b/tools/perf/pmu-events/arch/powerpc/power8/memory.json
index 2ba33420e20d..1d8241b8dc57 100644
--- a/tools/perf/pmu-events/arch/powerpc/power8/memory.json
+++ b/tools/perf/pmu-events/arch/powerpc/power8/memory.json
@@ -152,7 +152,7 @@
   {
     "EventCode": "0x1c05e",
     "EventName": "PM_MEM_LOC_THRESH_LSU_MED",
-    "BriefDescription": "Local memory above theshold for data prefetch",
+    "BriefDescription": "Local memory above threshold for data prefetch",
     "PublicDescription": ""
   },
   {
diff --git a/tools/perf/pmu-events/arch/powerpc/power8/metrics.json b/tools/perf/pmu-events/arch/powerpc/power8/metrics.json
index 4e25525b7da6..e5f9dbf199ac 100644
--- a/tools/perf/pmu-events/arch/powerpc/power8/metrics.json
+++ b/tools/perf/pmu-events/arch/powerpc/power8/metrics.json
@@ -30,7 +30,7 @@
         "MetricName": "ccache_mispredict_rate_percent"
     },
     {
-        "BriefDescription": "Percent of count catch mispredictions out of all completed branches that required count cache predictionn",
+        "BriefDescription": "Percent of count cache mispredictions out of all completed branches that required count cache prediction",
         "MetricExpr": "PM_BR_MPRED_CCACHE / (PM_BR_PRED_CCACHE_BR0 + PM_BR_PRED_CCACHE_BR1) * 100",
         "MetricGroup": "branch_prediction",
         "MetricName": "ccache_misprediction_percent"
@@ -969,7 +969,7 @@
         "MetricName": "l2_inst_miss_rate_percent"
     },
     {
-        "BriefDescription": "L2 dmand  Load Miss Rate (per run instruction)(%)",
+        "BriefDescription": "L2 demand  Load Miss Rate (per run instruction)(%)",
         "MetricExpr": "PM_DATA_FROM_L2MISS * 100 / PM_RUN_INST_CMPL",
         "MetricGroup": "general",
         "MetricName": "l2_ld_miss_rate_percent"
@@ -1215,7 +1215,7 @@
         "MetricName": "stores_per_inst"
     },
     {
-        "BriefDescription": "Icache Fetchs per Icache Miss",
+        "BriefDescription": "Icache Fetches per Icache Miss",
         "MetricExpr": "(PM_L1_ICACHE_MISS - PM_IC_PREF_WRITE) / PM_L1_ICACHE_MISS",
         "MetricGroup": "instruction_stats_percent_per_ref",
         "MetricName": "icache_miss_reload"
@@ -2003,7 +2003,7 @@
         "MetricName": "expansion_overhead_cpi"
     },
     {
-        "BriefDescription": "Total Fixed point operations executded in the Load/Store Unit following a load/store operation",
+        "BriefDescription": "Total Fixed point operations executed in the Load/Store Unit following a load/store operation",
         "MetricExpr": "PM_LSU_FX_FIN/PM_RUN_INST_CMPL",
         "MetricName": "fixed_in_lsu_per_inst"
     },
diff --git a/tools/perf/pmu-events/arch/powerpc/power8/other.json b/tools/perf/pmu-events/arch/powerpc/power8/other.json
index f1f2965f6775..6fef23e40658 100644
--- a/tools/perf/pmu-events/arch/powerpc/power8/other.json
+++ b/tools/perf/pmu-events/arch/powerpc/power8/other.json
@@ -212,13 +212,13 @@
   {
     "EventCode": "0x40a0",
     "EventName": "PM_BR_UNCOND_BR0",
-    "BriefDescription": "Unconditional Branch Completed on BR0. HW branch prediction was not used for this branch. This can be an I-form branch, a B-form branch with BO-field set to branch always, or a B-form branch which was coverted to a Resolve",
+    "BriefDescription": "Unconditional Branch Completed on BR0. HW branch prediction was not used for this branch. This can be an I-form branch, a B-form branch with BO-field set to branch always, or a B-form branch which was converted to a Resolve",
     "PublicDescription": ""
   },
   {
     "EventCode": "0x40a2",
     "EventName": "PM_BR_UNCOND_BR1",
-    "BriefDescription": "Unconditional Branch Completed on BR1. HW branch prediction was not used for this branch. This can be an I-form branch, a B-form branch with BO-field set to branch always, or a B-form branch which was coverted to a Resolve",
+    "BriefDescription": "Unconditional Branch Completed on BR1. HW branch prediction was not used for this branch. This can be an I-form branch, a B-form branch with BO-field set to branch always, or a B-form branch which was converted to a Resolve",
     "PublicDescription": ""
   },
   {
@@ -656,7 +656,7 @@
   {
     "EventCode": "0x4e050",
     "EventName": "PM_DC_PREF_STREAM_FUZZY_CONF",
-    "BriefDescription": "A demand load referenced a line in an active fuzzy prefetch stream. The stream could have been allocated through the hardware prefetch mechanism or through software.Fuzzy stream confirm (out of order effects, or pf cant keep up)",
+    "BriefDescription": "A demand load referenced a line in an active fuzzy prefetch stream. The stream could have been allocated through the hardware prefetch mechanism or through software. Fuzzy stream confirm (out of order effects, or pf can't keep up)",
     "PublicDescription": ""
   },
   {
@@ -1095,7 +1095,7 @@
     "EventCode": "0x1000a",
     "EventName": "PM_GRP_BR_MPRED_NONSPEC",
     "BriefDescription": "Group experienced non-speculative branch redirect",
-    "PublicDescription": "Group experienced Non-speculative br mispredicct"
+    "PublicDescription": "Group experienced Non-speculative br mispredict"
   },
   {
     "EventCode": "0x30004",
@@ -1113,7 +1113,7 @@
     "EventCode": "0x1000c",
     "EventName": "PM_GRP_IC_MISS_NONSPEC",
     "BriefDescription": "Group experienced non-speculative I cache miss",
-    "PublicDescription": "Group experi enced Non-specu lative I cache miss"
+    "PublicDescription": "Group experienced Non-speculative I cache miss"
   },
   {
     "EventCode": "0x10130",
@@ -1136,7 +1136,7 @@
   {
     "EventCode": "0x50a6",
     "EventName": "PM_GRP_TERM_FPU_AFTER_BR",
-    "BriefDescription": "There were enough instructions in the Ibuffer, but FPU OP IN same group after a branch terminates a group, cant do partial flushes",
+    "BriefDescription": "There were enough instructions in the Ibuffer, but FPU OP IN same group after a branch terminates a group, can't do partial flushes",
     "PublicDescription": ""
   },
   {
@@ -1220,7 +1220,7 @@
   {
     "EventCode": "0x4096",
     "EventName": "PM_IC_RELOAD_PRIVATE",
-    "BriefDescription": "Reloading line was brought in private for a specific thread. Most lines are brought in shared for all eight thrreads. If RA does not match then invalidates and then brings it shared to other thread. In P7 line brought in private , then line was invalidat",
+    "BriefDescription": "Reloading line was brought in private for a specific thread. Most lines are brought in shared for all eight threads. If RA does not match then invalidates and then brings it shared to other thread. In P7 line brought in private , then line was invalidated",
     "PublicDescription": ""
   },
   {
@@ -1664,25 +1664,25 @@
   {
     "EventCode": "0x200301ea",
     "EventName": "PM_L1MISS_LAT_EXC_1024",
-    "BriefDescription": "L1 misses that took longer than 1024 cyles to resolve (miss to reload)",
+    "BriefDescription": "L1 misses that took longer than 1024 cycles to resolve (miss to reload)",
     "PublicDescription": "Reload latency exceeded 1024 cyc"
   },
   {
     "EventCode": "0x200401ec",
     "EventName": "PM_L1MISS_LAT_EXC_2048",
-    "BriefDescription": "L1 misses that took longer than 2048 cyles to resolve (miss to reload)",
+    "BriefDescription": "L1 misses that took longer than 2048 cycles to resolve (miss to reload)",
     "PublicDescription": "Reload latency exceeded 2048 cyc"
   },
   {
     "EventCode": "0x200101e8",
     "EventName": "PM_L1MISS_LAT_EXC_256",
-    "BriefDescription": "L1 misses that took longer than 256 cyles to resolve (miss to reload)",
+    "BriefDescription": "L1 misses that took longer than 256 cycles to resolve (miss to reload)",
     "PublicDescription": "Reload latency exceeded 256 cyc"
   },
   {
     "EventCode": "0x200201e6",
     "EventName": "PM_L1MISS_LAT_EXC_32",
-    "BriefDescription": "L1 misses that took longer than 32 cyles to resolve (miss to reload)",
+    "BriefDescription": "L1 misses that took longer than 32 cycles to resolve (miss to reload)",
     "PublicDescription": "Reload latency exceeded 32 cyc"
   },
   {
@@ -1694,7 +1694,7 @@
   {
     "EventCode": "0x408c",
     "EventName": "PM_L1_DEMAND_WRITE",
-    "BriefDescription": "Instruction Demand sectors wriittent into IL1",
+    "BriefDescription": "Instruction Demand sectors written into IL1",
     "PublicDescription": ""
   },
   {
@@ -1874,7 +1874,7 @@
   {
     "EventCode": "0x3e052",
     "EventName": "PM_L3_SW_PREF",
-    "BriefDescription": "Data stream touchto L3",
+    "BriefDescription": "Data stream touch to L3",
     "PublicDescription": ""
   },
   {
@@ -2793,7 +2793,7 @@
     "EventCode": "0x2001a",
     "EventName": "PM_NTCG_ALL_FIN",
     "BriefDescription": "Cycles after all instructions have finished to group completed",
-    "PublicDescription": "Ccycles after all instructions have finished to group completed"
+    "PublicDescription": "Cycles after all instructions have finished to group completed"
   },
   {
     "EventCode": "0x20ac",
@@ -2877,7 +2877,7 @@
     "EventCode": "0x200101e8",
     "EventName": "PM_RC_LIFETIME_EXC_256",
     "BriefDescription": "Number of times the RC machine for a sampled instruction was active for more than 256 cycles",
-    "PublicDescription": "Threshold counter exceed a count of 256"
+    "PublicDescription": "Threshold counter exceeded a count of 256"
   },
   {
     "EventCode": "0x200201e6",
@@ -3092,8 +3092,8 @@
   {
     "EventCode": "0xe0b8",
     "EventName": "PM_TM_FAIL_NON_TX_CONFLICT",
-    "BriefDescription": "Non transactional conflict from LSU whtver gets repoted to texas",
-    "PublicDescription": "Non transactional conflict from LSU whtver gets repoted to texas42"
+    "BriefDescription": "Non transactional conflict from LSU whatever gets reported to texas",
+    "PublicDescription": "Non transactional conflict from LSU whatever gets reported to texas42"
   },
   {
     "EventCode": "0x308a",
@@ -3140,8 +3140,8 @@
   {
     "EventCode": "0xe08e",
     "EventName": "PM_UP_PREF_POINTER",
-    "BriefDescription": "Micrpartition pointer prefetches",
-    "PublicDescription": "Micrpartition pointer prefetches42"
+    "BriefDescription": "Micropartition pointer prefetches",
+    "PublicDescription": "Micropartition pointer prefetches42"
   },
   {
     "EventCode": "0xa0a4",
diff --git a/tools/perf/pmu-events/arch/powerpc/power8/pipeline.json b/tools/perf/pmu-events/arch/powerpc/power8/pipeline.json
index 0acfaaef4772..12689e8fb0b5 100644
--- a/tools/perf/pmu-events/arch/powerpc/power8/pipeline.json
+++ b/tools/perf/pmu-events/arch/powerpc/power8/pipeline.json
@@ -116,7 +116,7 @@
   {
     "EventCode": "0x30006",
     "EventName": "PM_CMPLU_STALL_OTHER_CMPL",
-    "BriefDescription": "Instructions core completed while this tread was stalled",
+    "BriefDescription": "Instructions core completed while this thread was stalled",
     "PublicDescription": "Instructions core completed while this thread was stalled"
   },
   {
@@ -189,7 +189,7 @@
     "EventCode": "0x3405e",
     "EventName": "PM_IFETCH_THROTTLE",
     "BriefDescription": "Cycles in which Instruction fetch throttle was active",
-    "PublicDescription": "Cycles instruction fecth was throttled in IFU"
+    "PublicDescription": "Cycles instruction fetch was throttled in IFU"
   },
   {
     "EventCode": "0x10014",
diff --git a/tools/perf/pmu-events/arch/powerpc/power8/pmc.json b/tools/perf/pmu-events/arch/powerpc/power8/pmc.json
index 5e0469f68bea..4e416878417d 100644
--- a/tools/perf/pmu-events/arch/powerpc/power8/pmc.json
+++ b/tools/perf/pmu-events/arch/powerpc/power8/pmc.json
@@ -98,7 +98,7 @@
   {
     "EventCode": "0x101e8",
     "EventName": "PM_THRESH_EXC_256",
-    "BriefDescription": "Threshold counter exceed a count of 256",
+    "BriefDescription": "Threshold counter exceeded a count of 256",
     "PublicDescription": ""
   },
   {
@@ -110,7 +110,7 @@
   {
     "EventCode": "0x101e6",
     "EventName": "PM_THRESH_EXC_4096",
-    "BriefDescription": "Threshold counter exceed a count of 4096",
+    "BriefDescription": "Threshold counter exceeded a count of 4096",
     "PublicDescription": ""
   },
   {
diff --git a/tools/perf/pmu-events/arch/powerpc/power9/cache.json b/tools/perf/pmu-events/arch/powerpc/power9/cache.json
index 2984190c2118..71dbed868c80 100644
--- a/tools/perf/pmu-events/arch/powerpc/power9/cache.json
+++ b/tools/perf/pmu-events/arch/powerpc/power9/cache.json
@@ -72,7 +72,7 @@
   {
     "EventCode": "0x101E6",
     "EventName": "PM_THRESH_EXC_4096",
-    "BriefDescription": "Threshold counter exceed a count of 4096"
+    "BriefDescription": "Threshold counter exceeded a count of 4096"
   },
   {
     "EventCode": "0x3F14A",
diff --git a/tools/perf/pmu-events/arch/powerpc/power9/frontend.json b/tools/perf/pmu-events/arch/powerpc/power9/frontend.json
index c8add9dfaa64..53a29e1c6c31 100644
--- a/tools/perf/pmu-events/arch/powerpc/power9/frontend.json
+++ b/tools/perf/pmu-events/arch/powerpc/power9/frontend.json
@@ -7,7 +7,7 @@
   {
     "EventCode": "0x101E8",
     "EventName": "PM_THRESH_EXC_256",
-    "BriefDescription": "Threshold counter exceed a count of 256"
+    "BriefDescription": "Threshold counter exceeded a count of 256"
   },
   {
     "EventCode": "0x4504E",
diff --git a/tools/perf/pmu-events/arch/powerpc/power9/marked.json b/tools/perf/pmu-events/arch/powerpc/power9/marked.json
index b24d25aba2df..aad23b00be92 100644
--- a/tools/perf/pmu-events/arch/powerpc/power9/marked.json
+++ b/tools/perf/pmu-events/arch/powerpc/power9/marked.json
@@ -402,7 +402,7 @@
   {
     "EventCode": "0x30006",
     "EventName": "PM_CMPLU_STALL_OTHER_CMPL",
-    "BriefDescription": "Instructions the core completed while this tread was stalled"
+    "BriefDescription": "Instructions the core completed while this thread was stalled"
   },
   {
     "EventCode": "0x1005C",
@@ -432,7 +432,7 @@
   {
     "EventCode": "0x400FC",
     "EventName": "PM_ITLB_MISS",
-    "BriefDescription": "ITLB Reloaded. Counts 1 per ITLB miss for HPT but multiple for radix depending on number of levels traveresed"
+    "BriefDescription": "ITLB Reloaded. Counts 1 per ITLB miss for HPT but multiple for radix depending on number of levels traversed"
   },
   {
     "EventCode": "0x1E044",
diff --git a/tools/perf/pmu-events/arch/powerpc/power9/metrics.json b/tools/perf/pmu-events/arch/powerpc/power9/metrics.json
index db86ba36224d..c405bf65d2f9 100644
--- a/tools/perf/pmu-events/arch/powerpc/power9/metrics.json
+++ b/tools/perf/pmu-events/arch/powerpc/power9/metrics.json
@@ -226,7 +226,7 @@
         "MetricName": "ict_noslot_cyc_other_cpi"
     },
     {
-        "BriefDescription": "Cycles in which the NTC instruciton is held at dispatch for any reason",
+        "BriefDescription": "Cycles in which the NTC instruction is held at dispatch for any reason",
         "MetricExpr": "PM_ICT_NOSLOT_DISP_HELD/PM_RUN_INST_CMPL",
         "MetricGroup": "cpi_breakdown",
         "MetricName": "ict_noslot_disp_held_cpi"
@@ -958,7 +958,7 @@
         "MetricName": "l2_inst_miss_rate_percent"
     },
     {
-        "BriefDescription": "L2 dmand Load Miss Rate (per run instruction)(%)",
+        "BriefDescription": "L2 demand Load Miss Rate (per run instruction)(%)",
         "MetricExpr": "PM_DATA_FROM_L2MISS * 100 / PM_RUN_INST_CMPL",
         "MetricGroup": "general",
         "MetricName": "l2_ld_miss_rate_percent"
@@ -1102,7 +1102,7 @@
         "MetricName": "l1_inst_miss_rate_percent"
     },
     {
-        "BriefDescription": "Icache Fetchs per Icache Miss",
+        "BriefDescription": "Icache Fetches per Icache Miss",
         "MetricExpr": "(PM_L1_ICACHE_MISS - PM_IC_PREF_WRITE) / PM_L1_ICACHE_MISS",
         "MetricGroup": "instruction_stats_percent_per_ref",
         "MetricName": "icache_miss_reload"
diff --git a/tools/perf/pmu-events/arch/powerpc/power9/other.json b/tools/perf/pmu-events/arch/powerpc/power9/other.json
index f10bd554521a..9fee9dfaa32f 100644
--- a/tools/perf/pmu-events/arch/powerpc/power9/other.json
+++ b/tools/perf/pmu-events/arch/powerpc/power9/other.json
@@ -57,7 +57,7 @@
   {
     "EventCode": "0xF8AC",
     "EventName": "PM_DC_DEALLOC_NO_CONF",
-    "BriefDescription": "A demand load referenced a line in an active fuzzy prefetch stream. The stream could have been allocated through the hardware prefetch mechanism or through software.Fuzzy stream confirm (out of order effects, or pf cant keep up)"
+    "BriefDescription": "A demand load referenced a line in an active fuzzy prefetch stream. The stream could have been allocated through the hardware prefetch mechanism or through software. Fuzzy stream confirm (out of order effects, or pf can't keep up)"
   },
   {
     "EventCode": "0xD090",
@@ -277,7 +277,7 @@
   {
     "EventCode": "0xF0BC",
     "EventName": "PM_LS2_UNALIGNED_ST",
-    "BriefDescription": "Store instructions whose data crosses a double-word boundary, which causes it to require an additional slice than than what normally would be required of the Store of that size.  If the Store wraps from slice 3 to slice 0, thee is an additional 3-cycle penalty"
+    "BriefDescription": "Store instructions whose data crosses a double-word boundary, which causes it to require an additional slice than what normally would be required of the Store of that size.  If the Store wraps from slice 3 to slice 0, there is an additional 3-cycle penalty"
   },
   {
     "EventCode": "0xD0AC",
@@ -297,7 +297,7 @@
   {
     "EventCode": "0x26082",
     "EventName": "PM_L2_IC_INV",
-    "BriefDescription": "I-cache Invalidates sent over the realod bus to the core"
+    "BriefDescription": "I-cache Invalidates sent over the reload bus to the core"
   },
   {
     "EventCode": "0xC8AC",
@@ -392,7 +392,7 @@
   {
     "EventCode": "0xC098",
     "EventName": "PM_LS2_UNALIGNED_LD",
-    "BriefDescription": "Load instructions whose data crosses a double-word boundary, which causes it to require an additional slice than than what normally would be required of the load of that size.  If the load wraps from slice 3 to slice 0, thee is an additional 3-cycle penalty"
+    "BriefDescription": "Load instructions whose data crosses a double-word boundary, which causes it to require an additional slice than what normally would be required of the load of that size.  If the load wraps from slice 3 to slice 0, there is an additional 3-cycle penalty"
   },
   {
     "EventCode": "0x20058",
@@ -472,12 +472,12 @@
   {
     "EventCode": "0xC094",
     "EventName": "PM_LS0_UNALIGNED_LD",
-    "BriefDescription": "Load instructions whose data crosses a double-word boundary, which causes it to require an additional slice than than what normally would be required of the load of that size.  If the load wraps from slice 3 to slice 0, thee is an additional 3-cycle penalty"
+    "BriefDescription": "Load instructions whose data crosses a double-word boundary, which causes it to require an additional slice than what normally would be required of the load of that size.  If the load wraps from slice 3 to slice 0, there is an additional 3-cycle penalty"
   },
   {
     "EventCode": "0xF8BC",
     "EventName": "PM_LS3_UNALIGNED_ST",
-    "BriefDescription": "Store instructions whose data crosses a double-word boundary, which causes it to require an additional slice than than what normally would be required of the Store of that size.  If the Store wraps from slice 3 to slice 0, thee is an additional 3-cycle penalty"
+    "BriefDescription": "Store instructions whose data crosses a double-word boundary, which causes it to require an additional slice than what normally would be required of the Store of that size.  If the Store wraps from slice 3 to slice 0, there is an additional 3-cycle penalty"
   },
   {
     "EventCode": "0x460AE",
@@ -512,12 +512,12 @@
   {
     "EventCode": "0x40A0",
     "EventName": "PM_BR_UNCOND",
-    "BriefDescription": "Unconditional Branch Completed. HW branch prediction was not used for this branch. This can be an I-form branch, a B-form branch with BO-field set to branch always, or a B-form branch which was covenrted to a Resolve."
+    "BriefDescription": "Unconditional Branch Completed. HW branch prediction was not used for this branch. This can be an I-form branch, a B-form branch with BO-field set to branch always, or a B-form branch which was converted to a Resolve."
   },
   {
     "EventCode": "0xF8A8",
     "EventName": "PM_DC_PREF_FUZZY_CONF",
-    "BriefDescription": "A demand load referenced a line in an active fuzzy prefetch stream. The stream could have been allocated through the hardware prefetch mechanism or through software.Fuzzy stream confirm (out of order effects, or pf cant keep up)"
+    "BriefDescription": "A demand load referenced a line in an active fuzzy prefetch stream. The stream could have been allocated through the hardware prefetch mechanism or through software. Fuzzy stream confirm (out of order effects, or pf can't keep up)"
   },
   {
     "EventCode": "0xF8A4",
@@ -647,7 +647,7 @@
   {
     "EventCode": "0x4894",
     "EventName": "PM_IC_RELOAD_PRIVATE",
-    "BriefDescription": "Reloading line was brought in private for a specific thread.  Most lines are brought in shared for all eight threads.  If RA does not match then invalidates and then brings it shared to other thread. In P7 line brought in private , then line was invalidat"
+    "BriefDescription": "Reloading line was brought in private for a specific thread.  Most lines are brought in shared for all eight threads.  If RA does not match then invalidates and then brings it shared to other thread. In P7 line brought in private , then line was invalidated"
   },
   {
     "EventCode": "0x1688E",
@@ -707,7 +707,7 @@
   {
     "EventCode": "0xF8B8",
     "EventName": "PM_LS1_UNALIGNED_ST",
-    "BriefDescription": "Store instructions whose data crosses a double-word boundary, which causes it to require an additional slice than than what normally would be required of the Store of that size.  If the Store wraps from slice 3 to slice 0, thee is an additional 3-cycle penalty"
+    "BriefDescription": "Store instructions whose data crosses a double-word boundary, which causes it to require an additional slice than what normally would be required of the Store of that size.  If the Store wraps from slice 3 to slice 0, there is an additional 3-cycle penalty"
   },
   {
     "EventCode": "0x408C",
@@ -887,7 +887,7 @@
   {
     "EventCode": "0xC898",
     "EventName": "PM_LS3_UNALIGNED_LD",
-    "BriefDescription": "Load instructions whose data crosses a double-word boundary, which causes it to require an additional slice than than what normally would be required of the load of that size.  If the load wraps from slice 3 to slice 0, thee is an additional 3-cycle penalty"
+    "BriefDescription": "Load instructions whose data crosses a double-word boundary, which causes it to require an additional slice than what normally would be required of the load of that size.  If the load wraps from slice 3 to slice 0, there is an additional 3-cycle penalty"
   },
   {
     "EventCode": "0x488C",
@@ -1117,7 +1117,7 @@
   {
     "EventCode": "0x50A4",
     "EventName": "PM_FLUSH_MPRED",
-    "BriefDescription": "Branch mispredict flushes.  Includes target and address misprecition"
+    "BriefDescription": "Branch mispredict flushes.  Includes target and address misprediction"
   },
   {
     "EventCode": "0x1504C",
@@ -1262,7 +1262,7 @@
   {
     "EventCode": "0xC894",
     "EventName": "PM_LS1_UNALIGNED_LD",
-    "BriefDescription": "Load instructions whose data crosses a double-word boundary, which causes it to require an additional slice than than what normally would be required of the load of that size.  If the load wraps from slice 3 to slice 0, thee is an additional 3-cycle penalty"
+    "BriefDescription": "Load instructions whose data crosses a double-word boundary, which causes it to require an additional slice than what normally would be required of the load of that size.  If the load wraps from slice 3 to slice 0, there is an additional 3-cycle penalty"
   },
   {
     "EventCode": "0x360A2",
@@ -2072,7 +2072,7 @@
   {
     "EventCode": "0xF0B8",
     "EventName": "PM_LS0_UNALIGNED_ST",
-    "BriefDescription": "Store instructions whose data crosses a double-word boundary, which causes it to require an additional slice than than what normally would be required of the Store of that size.  If the Store wraps from slice 3 to slice 0, thee is an additional 3-cycle penalty"
+    "BriefDescription": "Store instructions whose data crosses a double-word boundary, which causes it to require an additional slice than what normally would be required of the Store of that size.  If the Store wraps from slice 3 to slice 0, there is an additional 3-cycle penalty"
   },
   {
     "EventCode": "0x20132",
diff --git a/tools/perf/pmu-events/arch/powerpc/power9/translation.json b/tools/perf/pmu-events/arch/powerpc/power9/translation.json
index 2360b5afec6b..ab38d157540c 100644
--- a/tools/perf/pmu-events/arch/powerpc/power9/translation.json
+++ b/tools/perf/pmu-events/arch/powerpc/power9/translation.json
@@ -17,7 +17,7 @@
   {
     "EventCode": "0x4D05C",
     "EventName": "PM_DP_QP_FLOP_CMPL",
-    "BriefDescription": "Double-Precion or Quad-Precision instruction completed"
+    "BriefDescription": "Double-Precision or Quad-Precision instruction completed"
   },
   {
     "EventCode": "0x4E04C",
-- 
2.53.0


^ permalink raw reply related	[flat|nested] 7+ messages in thread

* [PATCH 2/3] perf vendor events intel: Fix misspellings in the Intel model tables
  2026-11-20 17:58 [PATCH 0/3] perf vendor events: Fix misspellings in event and metric descriptions TAKANO Mitsuhiro
  2026-11-20 17:58 ` [PATCH 1/3] perf vendor events powerpc: Fix misspellings in the power tables TAKANO Mitsuhiro
@ 2026-11-20 17:58 ` 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
  2 siblings, 1 reply; 7+ messages in thread
From: TAKANO Mitsuhiro @ 2026-11-20 17:58 UTC (permalink / raw)
  To: linux-perf-users, Peter Zijlstra, Ingo Molnar,
	Arnaldo Carvalho de Melo, Namhyung Kim
  Cc: Ian Rogers, Mark Rutland, Alexander Shishkin, Jiri Olsa,
	Adrian Hunter, James Clark, linux-kernel, TAKANO Mitsuhiro

Five descriptions are misspelled: "Prediciton" instead of "Prediction"
four times (the BPU_CLEARS.EARLY event in the westmereep-dp,
westmereep-sp, nehalemep and nehalemex pipeline tables), and "contoller"
instead of "controller" in the sierraforest srf-metrics table.  Four of
the five are event descriptions, which `perf list` prints as they are; the
fifth is a metric description, printed by `perf list metric`.

Only the descriptions change.  Regenerating the tables with

  jevents.py x86 all tools/perf/pmu-events/arch out.c out-str.c

leaves every event name and event code untouched, and the generated
out-str.c shrinks by 477 bytes, because the corrected text becomes
identical to descriptions that were already stored for other models and
the duplicates are dropped.

Signed-off-by: TAKANO Mitsuhiro <takano32@gmail.com>
---
 tools/perf/pmu-events/arch/x86/nehalemep/pipeline.json       | 2 +-
 tools/perf/pmu-events/arch/x86/nehalemex/pipeline.json       | 2 +-
 tools/perf/pmu-events/arch/x86/sierraforest/srf-metrics.json | 2 +-
 tools/perf/pmu-events/arch/x86/westmereep-dp/pipeline.json   | 2 +-
 tools/perf/pmu-events/arch/x86/westmereep-sp/pipeline.json   | 2 +-
 5 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/tools/perf/pmu-events/arch/x86/nehalemep/pipeline.json b/tools/perf/pmu-events/arch/x86/nehalemep/pipeline.json
index 869c84fa7c60..af823669fe71 100644
--- a/tools/perf/pmu-events/arch/x86/nehalemep/pipeline.json
+++ b/tools/perf/pmu-events/arch/x86/nehalemep/pipeline.json
@@ -51,7 +51,7 @@
         "UMask": "0x1"
     },
     {
-        "BriefDescription": "Early Branch Prediciton Unit clears",
+        "BriefDescription": "Early Branch Prediction Unit clears",
         "Counter": "0,1,2,3",
         "EventCode": "0xE8",
         "EventName": "BPU_CLEARS.EARLY",
diff --git a/tools/perf/pmu-events/arch/x86/nehalemex/pipeline.json b/tools/perf/pmu-events/arch/x86/nehalemex/pipeline.json
index 869c84fa7c60..af823669fe71 100644
--- a/tools/perf/pmu-events/arch/x86/nehalemex/pipeline.json
+++ b/tools/perf/pmu-events/arch/x86/nehalemex/pipeline.json
@@ -51,7 +51,7 @@
         "UMask": "0x1"
     },
     {
-        "BriefDescription": "Early Branch Prediciton Unit clears",
+        "BriefDescription": "Early Branch Prediction Unit clears",
         "Counter": "0,1,2,3",
         "EventCode": "0xE8",
         "EventName": "BPU_CLEARS.EARLY",
diff --git a/tools/perf/pmu-events/arch/x86/sierraforest/srf-metrics.json b/tools/perf/pmu-events/arch/x86/sierraforest/srf-metrics.json
index ca2c55917e55..a3d8c136334e 100644
--- a/tools/perf/pmu-events/arch/x86/sierraforest/srf-metrics.json
+++ b/tools/perf/pmu-events/arch/x86/sierraforest/srf-metrics.json
@@ -107,7 +107,7 @@
         "ScaleUnit": "1per_instr"
     },
     {
-        "BriefDescription": "Bandwidth observed by the integrated I/O traffic contoller (IIO) of IO reads that are initiated by end device controllers that are requesting memory from the CPU",
+        "BriefDescription": "Bandwidth observed by the integrated I/O traffic controller (IIO) of IO reads that are initiated by end device controllers that are requesting memory from the CPU",
         "MetricExpr": "UNC_IIO_DATA_REQ_OF_CPU.MEM_READ.ALL_PARTS * 4 / 1e6 / duration_time",
         "MetricName": "iio_bandwidth_read",
         "ScaleUnit": "1MB/s"
diff --git a/tools/perf/pmu-events/arch/x86/westmereep-dp/pipeline.json b/tools/perf/pmu-events/arch/x86/westmereep-dp/pipeline.json
index 0267788d9dce..e50ce906ed7b 100644
--- a/tools/perf/pmu-events/arch/x86/westmereep-dp/pipeline.json
+++ b/tools/perf/pmu-events/arch/x86/westmereep-dp/pipeline.json
@@ -51,7 +51,7 @@
         "UMask": "0x1"
     },
     {
-        "BriefDescription": "Early Branch Prediciton Unit clears",
+        "BriefDescription": "Early Branch Prediction Unit clears",
         "Counter": "0,1,2,3",
         "EventCode": "0xE8",
         "EventName": "BPU_CLEARS.EARLY",
diff --git a/tools/perf/pmu-events/arch/x86/westmereep-sp/pipeline.json b/tools/perf/pmu-events/arch/x86/westmereep-sp/pipeline.json
index 0267788d9dce..e50ce906ed7b 100644
--- a/tools/perf/pmu-events/arch/x86/westmereep-sp/pipeline.json
+++ b/tools/perf/pmu-events/arch/x86/westmereep-sp/pipeline.json
@@ -51,7 +51,7 @@
         "UMask": "0x1"
     },
     {
-        "BriefDescription": "Early Branch Prediciton Unit clears",
+        "BriefDescription": "Early Branch Prediction Unit clears",
         "Counter": "0,1,2,3",
         "EventCode": "0xE8",
         "EventName": "BPU_CLEARS.EARLY",
-- 
2.53.0


^ permalink raw reply related	[flat|nested] 7+ messages in thread

* [PATCH 3/3] perf vendor events amd: Fix a misspelling in the amdzen3 table
  2026-11-20 17:58 [PATCH 0/3] perf vendor events: Fix misspellings in event and metric descriptions TAKANO Mitsuhiro
  2026-11-20 17:58 ` [PATCH 1/3] perf vendor events powerpc: Fix misspellings in the power tables TAKANO Mitsuhiro
  2026-11-20 17:58 ` [PATCH 2/3] perf vendor events intel: Fix misspellings in the Intel model tables TAKANO Mitsuhiro
@ 2026-11-20 17:58 ` TAKANO Mitsuhiro
  2026-11-20 18:00   ` sashiko-bot
  2 siblings, 1 reply; 7+ messages in thread
From: TAKANO Mitsuhiro @ 2026-11-20 17:58 UTC (permalink / raw)
  To: linux-perf-users, Peter Zijlstra, Ingo Molnar,
	Arnaldo Carvalho de Melo, Namhyung Kim
  Cc: Ian Rogers, Mark Rutland, Alexander Shishkin, Jiri Olsa,
	Adrian Hunter, James Clark, linux-kernel, TAKANO Mitsuhiro

One word is misspelled in the amdzen3 branch table: "Instrcution" instead
of "Instruction" in the BriefDescription of bp_l1_tlb_fetch_hit.if4k, so
`perf list` prints the misspelling as it is.

Only the description changes.  Regenerating the tables with

  jevents.py x86 all tools/perf/pmu-events/arch out.c out-str.c

leaves the generated table and the string table identical except for that
one word: every event name and event code is untouched, and the string
table does not change size.

Signed-off-by: TAKANO Mitsuhiro <takano32@gmail.com>
---
 tools/perf/pmu-events/arch/x86/amdzen3/branch.json | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/perf/pmu-events/arch/x86/amdzen3/branch.json b/tools/perf/pmu-events/arch/x86/amdzen3/branch.json
index 018a7fe94fb9..a3b53845ca19 100644
--- a/tools/perf/pmu-events/arch/x86/amdzen3/branch.json
+++ b/tools/perf/pmu-events/arch/x86/amdzen3/branch.json
@@ -42,7 +42,7 @@
   {
     "EventName": "bp_l1_tlb_fetch_hit.if4k",
     "EventCode": "0x94",
-    "BriefDescription": "The number of instruction fetches that hit in the L1 ITLB. L1 Instrcution TLB hit (4K or 16K page size).",
+    "BriefDescription": "The number of instruction fetches that hit in the L1 ITLB. L1 Instruction TLB hit (4K or 16K page size).",
     "UMask": "0x01"
   },
   {
-- 
2.53.0


^ permalink raw reply related	[flat|nested] 7+ messages in thread

* Re: [PATCH 3/3] perf vendor events amd: Fix a misspelling in the amdzen3 table
  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
  0 siblings, 0 replies; 7+ messages in thread
From: sashiko-bot @ 2026-11-20 18:00 UTC (permalink / raw)
  To: TAKANO Mitsuhiro, linux-perf-users

> One word is misspelled in the amdzen3 branch table: "Instrcution" instead
> of "Instruction" in the BriefDescription of bp_l1_tlb_fetch_hit.if4k, so
> `perf list` prints the misspelling as it is.
> 
> Only the description changes.  Regenerating the tables with
> 
>   jevents.py x86 all tools/perf/pmu-events/arch out.c out-str.c
> 
> leaves the generated table and the string table identical except for that
> one word: every event name and event code is untouched, and the string
> table does not change size.
> 
> Signed-off-by: TAKANO Mitsuhiro <takano32@gmail.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261120175840.1274637-1-takano32@gmail.com?part=3


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [PATCH 2/3] perf vendor events intel: Fix misspellings in the Intel model tables
  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
  0 siblings, 0 replies; 7+ messages in thread
From: sashiko-bot @ 2026-11-20 18:01 UTC (permalink / raw)
  To: TAKANO Mitsuhiro, linux-perf-users

> Five descriptions are misspelled: "Prediciton" instead of "Prediction"
> four times (the BPU_CLEARS.EARLY event in the westmereep-dp,
> westmereep-sp, nehalemep and nehalemex pipeline tables), and "contoller"
> instead of "controller" in the sierraforest srf-metrics table.  Four of
> the five are event descriptions, which `perf list` prints as they are; the
> fifth is a metric description, printed by `perf list metric`.
> 
> Only the descriptions change.  Regenerating the tables with
> 
>   jevents.py x86 all tools/perf/pmu-events/arch out.c out-str.c
> 
> leaves every event name and event code untouched, and the generated
> out-str.c shrinks by 477 bytes, because the corrected text becomes
> identical to descriptions that were already stored for other models and
> the duplicates are dropped.
> 
> Signed-off-by: TAKANO Mitsuhiro <takano32@gmail.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261120175840.1274637-1-takano32@gmail.com?part=2


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [PATCH 1/3] perf vendor events powerpc: Fix misspellings in the power tables
  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
  0 siblings, 0 replies; 7+ messages in thread
From: sashiko-bot @ 2026-11-20 18:01 UTC (permalink / raw)
  To: TAKANO Mitsuhiro, linux-perf-users

> Thirty-two different words are wrong, 69 times in all, in 54 descriptions
> of the power8, power9 and power10 tables.  Fifteen of them appear more
> than once: "than than" and "thee" eight times each, "exceed" five times,
> "cyles", "finshed" and "cant" four times each, "software.Fuzzy" three
> times, and "coverted", "repoted", "Fetchs", "whtver", "Micrpartition",
> "dmand", "invalidat" and "tread" twice each; the other seventeen appear
> once.
> 
> 62 of the 69 are in BriefDescription fields and seven in PublicDescription
> fields, so `perf list` prints those 62 and `perf list -v` prints those
> seven.  Eleven of the 62 are metric descriptions, printed by `perf list
> metric`.
> 
> Sixteen of the 69 are not misspellings: eight are a doubled "than", four
> are missing spaces ("touchto" in "touch to L3", and "software.Fuzzy" in
> [ ... ]
> gone from the generated out-str.c, which shrinks by 393 bytes as some
> corrected descriptions become identical to ones already stored for other
> models.
> 
> Signed-off-by: TAKANO Mitsuhiro <takano32@gmail.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261120175840.1274637-1-takano32@gmail.com?part=1


^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2026-11-20 18:01 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-20 17:58 [PATCH 0/3] perf vendor events: Fix misspellings in event and metric descriptions TAKANO Mitsuhiro
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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.