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 0/4] perf vendor events amd: Add Zen 5 events and metrics
Date: Mon, 11 Mar 2024 10:53:14 +0530 [thread overview]
Message-ID: <cover.1710133771.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
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
.../pmu-events/arch/x86/amdzen5/branch.json | 82 ++
.../pmu-events/arch/x86/amdzen5/cache.json | 780 ++++++++++++++++
.../pmu-events/arch/x86/amdzen5/core.json | 122 +++
.../arch/x86/amdzen5/floating-point.json | 830 ++++++++++++++++++
.../arch/x86/amdzen5/memory-controller.json | 101 +++
.../pmu-events/arch/x86/amdzen5/memory.json | 180 ++++
.../pmu-events/arch/x86/amdzen5/other.json | 168 ++++
.../pmu-events/arch/x86/amdzen5/pipeline.json | 98 +++
.../arch/x86/amdzen5/recommended.json | 357 ++++++++
tools/perf/pmu-events/arch/x86/mapfile.csv | 1 +
10 files changed, 2719 insertions(+)
create mode 100644 tools/perf/pmu-events/arch/x86/amdzen5/branch.json
create mode 100644 tools/perf/pmu-events/arch/x86/amdzen5/cache.json
create mode 100644 tools/perf/pmu-events/arch/x86/amdzen5/core.json
create mode 100644 tools/perf/pmu-events/arch/x86/amdzen5/floating-point.json
create mode 100644 tools/perf/pmu-events/arch/x86/amdzen5/memory-controller.json
create mode 100644 tools/perf/pmu-events/arch/x86/amdzen5/memory.json
create mode 100644 tools/perf/pmu-events/arch/x86/amdzen5/other.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-03-11 5:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 5:23 Sandipan Das [this message]
2024-03-11 5:23 ` [PATCH 1/4] perf vendor events amd: Add Zen 5 core events Sandipan Das
2024-03-11 17:40 ` Ian Rogers
2024-03-12 9:59 ` Sandipan Das
2024-03-11 5:23 ` [PATCH 2/4] perf vendor events amd: Add Zen 5 uncore events Sandipan Das
2024-03-11 17:43 ` Ian Rogers
2024-03-12 10:02 ` Sandipan Das
2024-03-11 5:23 ` [PATCH 3/4] perf vendor events amd: Add Zen 5 metrics Sandipan Das
2024-03-11 18:46 ` Ian Rogers
2024-03-12 10:32 ` Sandipan Das
2024-03-11 5:23 ` [PATCH 4/4] perf vendor events amd: Add Zen 5 mapping Sandipan Das
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.1710133771.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).