From: James Clark <james.clark@arm.com>
To: linux-arm-kernel@lists.infradead.org, linux-perf-users@vger.kernel.org
Cc: James Clark <james.clark@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
Mark Rutland <mark.rutland@arm.com>,
Zaid Al-Bassam <zalbassam@google.com>,
Marc Zyngier <maz@kernel.org>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/2] arm64: perf: Add support for event counting threshold
Date: Tue, 19 Sep 2023 10:51:27 +0100 [thread overview]
Message-ID: <20230919095137.360963-1-james.clark@arm.com> (raw)
FEAT_PMUv3_TH (Armv8.8) is a new feature that allows conditional
counting of PMU events depending on how much the event increments on
a single cycle. Two new config fields for perf_event_open have been
added, and a PMU cap file for reading the max_threshold. See the first
commit message and the docs in the second commit for more details.
The change has been validated on the Arm FVP model:
# Zero values, works as expected (as before).
$ perf stat -e dtlb_walk/threshold=0,threshold_control=0/ -- true
5962 dtlb_walk/threshold=0,threshold_control=0/
# Threshold >= 255 causes count to be 0 because dtlb_walk doesn't
# increase by more than 1 per cycle.
$ perf stat -e dtlb_walk/threshold=255,threshold_control=5/ -- true
0 dtlb_walk/threshold=255,threshold_control=5/
# Keeping comparison as >= but lowering the threshold to 1 makes the
# count return.
$ perf stat -e dtlb_walk/threshold=1,threshold_control=5/ -- true
6329 dtlb_walk/threshold=1,threshold_control=5/
James Clark (2):
arm64: perf: Add support for event counting threshold
Documentation: arm64: Document the PMU event counting threshold
feature
Documentation/arch/arm64/perf.rst | 58 ++++++++++++++++++++++++++++++
drivers/perf/arm_pmuv3.c | 59 ++++++++++++++++++++++++++++++-
include/linux/perf/arm_pmuv3.h | 7 +++-
3 files changed, 122 insertions(+), 2 deletions(-)
base-commit: 21b61fe48c2fc43d98ebb67a1f3832e0478fa523
--
2.34.1
next reply other threads:[~2023-09-19 9:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 9:51 James Clark [this message]
2023-09-19 9:51 ` [PATCH v1 1/2] " James Clark
2023-10-09 12:50 ` Suzuki K Poulose
2023-10-09 16:30 ` James Clark
2023-10-10 11:03 ` Suzuki K Poulose
2023-10-10 12:48 ` James Clark
2023-09-19 9:51 ` [PATCH v1 2/2] Documentation: arm64: Document the PMU event counting threshold feature James Clark
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=20230919095137.360963-1-james.clark@arm.com \
--to=james.clark@arm.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=will@kernel.org \
--cc=zalbassam@google.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®