From: Sandipan Das <sandipan.das@amd.com>
To: <linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>, <x86@kernel.org>
Cc: <peterz@infradead.org>, <bp@alien8.de>, <acme@kernel.org>,
<namhyung@kernel.org>, <jolsa@kernel.org>, <tglx@linutronix.de>,
<mingo@redhat.com>, <pbonzini@redhat.com>, <jmattson@google.com>,
<like.xu.linux@gmail.com>, <eranian@google.com>,
<ananth.narayan@amd.com>, <ravi.bangoria@amd.com>,
<santosh.shukla@amd.com>, <sandipan.das@amd.com>
Subject: [PATCH 0/5] perf/x86/amd: Add PerfMonV2 DF ehnancements
Date: Thu, 19 May 2022 15:33:29 +0530 [thread overview]
Message-ID: <cover.1652954372.git.sandipan.das@amd.com> (raw)
Add support for using AMD Performance Monitoring Version 2
(PerfMonV2) features for Data Fabric (DF) events on Zen 4
processors. Utilize new CPUID leaf to detect PerfMonV2 and
determine the number of available PMCs. Also introduce the
new event encoding format and RDPMC mappings for accessing
additional DF counters.
E.g. larger metric groups which require more than 4 counters
could not be counted even on a Zen 4 platform that supports
16 DF counters. Only partial counting is possible by using
"--metric-no-group".
$ sudo perf stat -M nps1_die_to_dram true
Before:
Performance counter stats for 'system wide':
<not counted> dram_channel_data_controller_4 (0.00%)
<not counted> dram_channel_data_controller_1 (0.00%)
<not counted> dram_channel_data_controller_6 (0.00%)
<not counted> dram_channel_data_controller_3 (0.00%)
<not counted> dram_channel_data_controller_0 (0.00%)
<not counted> dram_channel_data_controller_5 (0.00%)
<not counted> dram_channel_data_controller_2 (0.00%)
<not counted> dram_channel_data_controller_7 (0.00%)
886817 ns duration_time
0.000886817 seconds time elapsed
After:
Performance counter stats for 'system wide':
0 dram_channel_data_controller_4 # 0.2 MiB nps1_die_to_dram
0 dram_channel_data_controller_1
0 dram_channel_data_controller_6
2838 dram_channel_data_controller_3
0 dram_channel_data_controller_0
0 dram_channel_data_controller_5
0 dram_channel_data_controller_2
0 dram_channel_data_controller_7
896438 ns duration_time
0.000896438 seconds time elapsed
Sandipan Das (5):
perf/x86/amd/uncore: Use dynamic events array
perf/x86/amd/uncore: Use attr_update for format attributes
perf/x86/amd/uncore: Detect available DF counters
perf/x86/amd/uncore: Add PerfMonV2 DF event format
perf/x86/amd/uncore: Add PerfMonV2 RDPMC assignments
arch/x86/events/amd/uncore.c | 146 ++++++++++++++++++++++++------
arch/x86/include/asm/perf_event.h | 16 ++++
2 files changed, 136 insertions(+), 26 deletions(-)
--
2.34.1
next reply other threads:[~2022-05-19 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-19 10:03 Sandipan Das [this message]
2022-05-19 10:03 ` [PATCH 1/5] perf/x86/amd/uncore: Use dynamic events array Sandipan Das
2022-05-19 10:03 ` [PATCH 2/5] perf/x86/amd/uncore: Use attr_update for format attributes Sandipan Das
2022-05-19 10:03 ` [PATCH 3/5] perf/x86/amd/uncore: Detect available DF counters Sandipan Das
2022-05-19 10:03 ` [PATCH 4/5] perf/x86/amd/uncore: Add PerfMonV2 DF event format Sandipan Das
2022-05-19 10:03 ` [PATCH 5/5] perf/x86/amd/uncore: Add PerfMonV2 RDPMC assignments 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.1652954372.git.sandipan.das@amd.com \
--to=sandipan.das@amd.com \
--cc=acme@kernel.org \
--cc=ananth.narayan@amd.com \
--cc=bp@alien8.de \
--cc=eranian@google.com \
--cc=jmattson@google.com \
--cc=jolsa@kernel.org \
--cc=like.xu.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=ravi.bangoria@amd.com \
--cc=santosh.shukla@amd.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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).