perf vendor events amd: Add Zen 5 events and metrics
Status from this message: Thanks, applied to perf-tools-next,
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest4 patches 1 replyApplied
- v14 patches 6 repliesSuperseded
Changes in v2 from the cover letter
- Categorize events based on their prefixes and rename the JSON files accordingly.
- Change metric scale units based on previous suggestions.
- Describe pipeline utilization metrics as percentages instead of fractions.
- Rename some pipeline utilization metrics ending with suffixes like "_bandwidth" or "_latency" to correctly denote that these are not actually reporting bandwidth or latency.
- Change branch misprediction ratio metric to misprediction rate.
- Remove some duplicate UMC metrics.
Patches in v2 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | perf vendor events amd: Add Zen 5 core eventstools/ tools/ tools/ +4 more | +1983 | 0 replies | |
| 2/4 | perf vendor events amd: Add Zen 5 uncore eventstools/ tools/ | +278 | 0 replies | |
| 3/4 | perf vendor events amd: Add Zen 5 metricstools/ tools/ | +444 | 0 replies | |
| 4/4 | perf vendor events amd: Add Zen 5 mappingtools/ | +1 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.
Cover letter [PATCH v2 0/4] perf vendor events amd: Add Zen 5 events and metrics
Add events and metrics taken from the Performance Monitor Counters for AMD Family 1Ah Model 00h-0Fh Processors document available at
https://bugzilla.kernel.org/attachment.cgi?id=305974
Previous versions can be found at:
v1: https://lore.kernel.org/all/[email protected]/
Changes in v2:
- Categorize events based on their prefixes and rename the JSON files accordingly.
- Change metric scale units based on previous suggestions.
- Describe pipeline utilization metrics as percentages instead of fractions.
- Rename some pipeline utilization metrics ending with suffixes like "_bandwidth" or "_latency" to correctly denote that these are not actually reporting bandwidth or latency.
- Change branch misprediction ratio metric to misprediction rate.
- Remove some duplicate UMC metrics.
Sandipan Das (4):
perf vendor events amd: Add Zen 5 core events
perf vendor events amd: Add Zen 5 uncore events
perf vendor events amd: Add Zen 5 metrics
perf vendor events amd: Add Zen 5 mapping
.../arch/x86/amdzen5/branch-prediction.json | 93 ++ .../pmu-events/arch/x86/amdzen5/decode.json | 115 +++ .../arch/x86/amdzen5/execution.json | 174 ++++ .../arch/x86/amdzen5/floating-point.json | 812 ++++++++++++++++++ .../arch/x86/amdzen5/inst-cache.json | 72 ++ .../pmu-events/arch/x86/amdzen5/l2-cache.json | 266 ++++++ .../pmu-events/arch/x86/amdzen5/l3-cache.json | 177 ++++ .../arch/x86/amdzen5/load-store.json | 451 ++++++++++ .../arch/x86/amdzen5/memory-controller.json | 101 +++ .../pmu-events/arch/x86/amdzen5/pipeline.json | 99 +++ .../arch/x86/amdzen5/recommended.json | 345 ++++++++ tools/perf/pmu-events/arch/x86/mapfile.csv | 1 + 12 files changed, 2706 insertions(+) create mode 100644 tools/perf/pmu-events/arch/x86/amdzen5/branch-prediction.json create mode 100644 tools/perf/pmu-events/arch/x86/amdzen5/decode.json create mode 100644 tools/perf/pmu-events/arch/x86/amdzen5/execution.json create mode 100644 tools/perf/pmu-events/arch/x86/amdzen5/floating-point.json create mode 100644 tools/perf/pmu-events/arch/x86/amdzen5/inst-cache.json create mode 100644 tools/perf/pmu-events/arch/x86/amdzen5/l2-cache.json create mode 100644 tools/perf/pmu-events/arch/x86/amdzen5/l3-cache.json create mode 100644 tools/perf/pmu-events/arch/x86/amdzen5/load-store.json create mode 100644 tools/perf/pmu-events/arch/x86/amdzen5/memory-controller.json create mode 100644 tools/perf/pmu-events/arch/x86/amdzen5/pipeline.json create mode 100644 tools/perf/pmu-events/arch/x86/amdzen5/recommended.json
Signature · 1 line
2.34.1