From: Ravi Bangoria <ravi.bangoria@amd.com>
To: Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>
Cc: Ravi Bangoria <ravi.bangoria@amd.com>,
Ingo Molnar <mingo@redhat.com>,
Stephane Eranian <eranian@google.com>,
Ian Rogers <irogers@google.com>,
"Kan Liang" <kan.liang@linux.intel.com>,
James Clark <james.clark@linaro.org>, "Leo Yan" <leo.yan@arm.com>,
Joe Mario <jmario@redhat.com>, <linux-kernel@vger.kernel.org>,
<linux-perf-users@vger.kernel.org>,
"Santosh Shukla" <santosh.shukla@amd.com>,
Ananth Narayan <ananth.narayan@amd.com>,
Sandipan Das <sandipan.das@amd.com>
Subject: [PATCH 4/4] perf doc amd: Update perf-amd-ibs man page
Date: Thu, 29 May 2025 12:34:56 +0000 [thread overview]
Message-ID: <20250529123456.1801-5-ravi.bangoria@amd.com> (raw)
In-Reply-To: <20250529123456.1801-1-ravi.bangoria@amd.com>
o Document software filtering capabilities provided by IBS kernel
driver.
o After recent perf-mem hist updates [1], the perf-mem example command
in the perf-amd-ibs man page renders output differently. Unfortunately,
there is no way to get the same aggregated output now. So use alternate
command that can aggregate and show data at the command level.
[1]: https://lore.kernel.org/r/20250430205548.789750-1-namhyung@kernel.org
Signed-off-by: Ravi Bangoria <ravi.bangoria@amd.com>
---
tools/perf/Documentation/perf-amd-ibs.txt | 72 +++++++++++++++++------
1 file changed, 54 insertions(+), 18 deletions(-)
diff --git a/tools/perf/Documentation/perf-amd-ibs.txt b/tools/perf/Documentation/perf-amd-ibs.txt
index 55f80beae037..a543a68e3c94 100644
--- a/tools/perf/Documentation/perf-amd-ibs.txt
+++ b/tools/perf/Documentation/perf-amd-ibs.txt
@@ -33,9 +33,6 @@ if IBS is supported by the hardware and kernel.
IBS Op PMU supports two events: cycles and micro ops. IBS Fetch PMU supports
one event: fetch ops.
-IBS PMUs do not have user/kernel filtering capability and thus it requires
-CAP_SYS_ADMIN or CAP_PERFMON privilege.
-
IBS VS. REGULAR CORE PMU
------------------------
@@ -160,6 +157,38 @@ System-wide profile, fetch ops event, sampling period: 100000, Random enable
etc.
+IBS SW FILTERING
+----------------
+
+IBS PMU driver provides few additional software filtering capabilities. When
+supported, kernel exposes config format through the following files:
+
+ /sys/bus/event_source/devices/ibs_fetch/format/swfilt
+ /sys/bus/event_source/devices/ibs_op/format/swfilt
+
+1. Privilege (user/kernel) filtering. IBS PMUs do not support privilege
+filtering in hardware so IBS driver supports it as a software filter.
+
+ ibs_op/swfilt=1/u --> Only usermode samples
+ ibs_op/swfilt=1/k --> Only kernelmode samples
+ ibs_fetch/swfilt=1/u --> Only usermode samples
+ ibs_fetch/swfilt=1/k --> Only kernelmode samples
+
+ Privilege filtering is always available when "swfilt" is supported.
+ So, kernel does not expose any separate PMU capability for this.
+
+2. Load/Store sampling. IBS OP PMU do not support load/store filtering in
+hardware, so IBS driver supports it as a software filter.
+
+ ibs_op/swfilt=1,ldop=1/ --> Only load samples
+ ibs_op/swfilt=1,stop=1/ --> Only store samples
+ ibs_op/swfilt=1,ldop=1,stop=1/ --> Load OR store samples
+
+ Kernel creates following PMU capability file when load/store software
+ filtering is supported:
+
+ /sys/bus/event_source/devices/ibs_op/caps/swfilt_ldst
+
PERF MEM AND PERF C2C
---------------------
@@ -173,21 +202,28 @@ Below is a simple example of the perf mem tool.
A normal perf mem report output will provide detailed memory access profile.
However, it can also be aggregated based on output fields. For example:
- # perf mem report -F mem,sample,snoop
- Samples: 3M of event 'ibs_op//', Event count (approx.): 23524876
- Memory access Samples Snoop
- N/A 1903343 N/A
- L1 hit 1056754 N/A
- L2 hit 75231 N/A
- L3 hit 9496 HitM
- L3 hit 2270 N/A
- RAM hit 8710 N/A
- Remote node, same socket RAM hit 3241 N/A
- Remote core, same node Any cache hit 1572 HitM
- Remote core, same node Any cache hit 514 N/A
- Remote node, same socket Any cache hit 1216 HitM
- Remote node, same socket Any cache hit 350 N/A
- Uncached hit 18 N/A
+ # perf mem report -s comm,mem -H --stdio
+ Overhead Samples Command / Memory access
+ ......................... ..........................................
+ 66.46% 471728 cc1
+ 34.70% 1393 RAM hit
+ 10.42% 370 Remote node, same socket RAM hit
+ 6.73% 10239 L2 hit
+ 5.84% 293953 N/A
+ 3.26% 163803 L1 hit
+ 3.16% 1796 L3 hit
+ 1.29% 95 Remote core, same node Any cache hit
+ 1.06% 73 Remote node, same socket Any cache hit
+ 0.00% 6 Uncached hit
+ 9.45% 44994 sh
+ 2.60% 131 RAM hit
+ 2.21% 219 Remote core, same node Any cache hit
+ 1.89% 190 Remote node, same socket Any cache hit
+ 1.02% 52 Remote node, same socket RAM hit
+ 0.72% 785 L2 hit
+ 0.60% 30149 N/A
+ 0.27% 13340 L1 hit
+ ...
Please refer to their man page for more detail.
--
2.43.0
prev parent reply other threads:[~2025-05-29 12:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-29 12:34 [PATCH 0/4] perf/amd/ibs: Introduce load/store SW filter Ravi Bangoria
2025-05-29 12:34 ` [PATCH 1/4] perf/amd/ibs: Add load/store SW filters to IBS OP PMU Ravi Bangoria
2025-05-31 7:53 ` Ingo Molnar
2025-06-03 6:52 ` Namhyung Kim
2025-06-10 5:12 ` Ravi Bangoria
2025-05-29 12:34 ` [PATCH 2/4] perf mem/c2c amd: Wire IBS OP PMU load/store SW filter Ravi Bangoria
2025-05-29 12:34 ` [PATCH 3/4] perf test amd: Add IBS load/store swfilt tests Ravi Bangoria
2025-05-29 12:34 ` Ravi Bangoria [this message]
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=20250529123456.1801-5-ravi.bangoria@amd.com \
--to=ravi.bangoria@amd.com \
--cc=acme@kernel.org \
--cc=ananth.narayan@amd.com \
--cc=eranian@google.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=jmario@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=sandipan.das@amd.com \
--cc=santosh.shukla@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
all inboxes | Powered by JetHome®