From: Sandipan Das <sandipan.das@amd.com>
To: <linux-perf-users@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <peterz@infradead.org>, <mingo@redhat.com>, <acme@kernel.org>,
<namhyung@kernel.org>, <mark.rutland@arm.com>,
<alexander.shishkin@linux.intel.com>, <jolsa@kernel.org>,
<irogers@google.com>, <adrian.hunter@intel.com>,
<eranian@google.com>, <ravi.bangoria@amd.com>,
<ananth.narayan@amd.com>, <sandipan.das@amd.com>
Subject: [PATCH v2 0/4] perf vendor events amd: Add Zen 5 events and metrics
Date: Fri, 3 May 2024 12:46:18 +0530 [thread overview]
Message-ID: <cover.1714717230.git.sandipan.das@amd.com> (raw)
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/cover.1710133771.git.sandipan.das@amd.com/
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
--
2.34.1
next reply other threads:[~2024-05-03 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 7:16 Sandipan Das [this message]
2024-05-03 7:16 ` [PATCH v2 1/4] perf vendor events amd: Add Zen 5 core events Sandipan Das
2024-05-03 7:16 ` [PATCH v2 2/4] perf vendor events amd: Add Zen 5 uncore events Sandipan Das
2024-05-03 7:16 ` [PATCH v2 3/4] perf vendor events amd: Add Zen 5 metrics Sandipan Das
2024-05-03 7:16 ` [PATCH v2 4/4] perf vendor events amd: Add Zen 5 mapping Sandipan Das
[not found] ` <CAP-5=fVqr9E_YS-V=1rnrxH3AchRy8x0wR9wSpSwLiUNuMij=A@mail.gmail.com>
2024-05-04 18:12 ` [PATCH v2 0/4] perf vendor events amd: Add Zen 5 events and metrics Arnaldo Carvalho de Melo
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=cover.1714717230.git.sandipan.das@amd.com \
--to=sandipan.das@amd.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ananth.narayan@amd.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--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 \
--cc=ravi.bangoria@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 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.