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/3] perf vendor events amd: Add more Zen 5 events and metrics
Date: Fri, 18 Oct 2024 15:01:02 +0530 [thread overview]
Message-ID: <cover.1729242778.git.sandipan.das@amd.com> (raw)
Add data fabric events and metrics taken from the now released Processor
Programming Reference (PPR) for AMD Family 1Ah Model 02h Revision C1
Processors document available at the link below.
https://bugzilla.kernel.org/attachment.cgi?id=307010
While at it, also update some missing or redundant data cache metrics.
Sandipan Das (3):
perf vendor events amd: Add Zen 5 data fabric events
perf vendor events amd: Add Zen 5 data fabric metrics
perf vendor events amd: Update Zen 5 data cache fill events
.../arch/x86/amdzen5/data-fabric.json | 1634 +++++++++++++++++
.../arch/x86/amdzen5/load-store.json | 78 +-
.../arch/x86/amdzen5/recommended.json | 112 ++
3 files changed, 1818 insertions(+), 6 deletions(-)
create mode 100644 tools/perf/pmu-events/arch/x86/amdzen5/data-fabric.json
--
2.43.0
next reply other threads:[~2024-10-18 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 9:31 Sandipan Das [this message]
2024-10-18 9:31 ` [PATCH 1/3] perf vendor events amd: Add Zen 5 data fabric events Sandipan Das
2024-10-18 9:31 ` [PATCH 2/3] perf vendor events amd: Add Zen 5 data fabric metrics Sandipan Das
2024-10-18 15:47 ` Ian Rogers
2024-10-18 9:31 ` [PATCH 3/3] perf vendor events amd: Update Zen 5 data cache fill events Sandipan Das
2024-10-18 15:48 ` [PATCH 0/3] perf vendor events amd: Add more Zen 5 events and metrics Ian Rogers
2024-10-21 16:01 ` Namhyung Kim
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.1729242778.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