From: Mark Rutland <mark.rutland@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: catalin.marinas@arm.com, will@kernel.org,
kvmarm@lists.cs.columbia.edu, maz@kernel.org
Subject: [PATCHv6 0/3] arm64: perf: Add support for ARMv8.5-PMU 64-bit counters
Date: Mon, 2 Mar 2020 18:17:49 +0000 [thread overview]
Message-ID: <20200302181752.14251-1-mark.rutland@arm.com> (raw)
This is a respin of Andrew Murray's series to enable support for 64-bit
counters as introduced in ARMv8.5.
I've given this a spin on (ARMv8.2) hardware, to test that there are no
regressions, but I have not had the chance to test in an ARMv8.5 model (which I
beleive Andrew had previously tested).
Since v5 [1]:
* Don't treat perfmon ID fields as signed
* Fix up ID field names
* Explicitly compare ARMV8.5 PMU value
[1] https://lkml.kernel.org/r/1580125469-23887-1-git-send-email-andrew.murray@arm.com
Thanks,
Mark.
Andrew Murray (3):
arm64: cpufeature: Extract capped perfmon fields
KVM: arm64: limit PMU version to PMUv3 for ARMv8.1
arm64: perf: Add support for ARMv8.5-PMU 64-bit counters
arch/arm64/include/asm/cpufeature.h | 23 ++++++++++
arch/arm64/include/asm/perf_event.h | 3 +-
arch/arm64/include/asm/sysreg.h | 10 +++++
arch/arm64/kernel/perf_event.c | 86 +++++++++++++++++++++++++++++--------
arch/arm64/kvm/sys_regs.c | 10 +++++
include/linux/perf/arm_pmu.h | 1 +
6 files changed, 115 insertions(+), 18 deletions(-)
--
2.11.0
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
next reply other threads:[~2020-03-02 18:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-02 18:17 Mark Rutland [this message]
2020-03-02 18:17 ` [PATCHv6 1/3] arm64: cpufeature: Extract capped perfmon fields Mark Rutland
2020-03-02 18:17 ` [PATCHv6 2/3] KVM: arm64: limit PMU version to PMUv3 for ARMv8.1 Mark Rutland
2020-03-02 18:17 ` [PATCHv6 3/3] arm64: perf: Add support for ARMv8.5-PMU 64-bit counters Mark Rutland
2020-03-03 19:07 ` [PATCHv6 0/3] " Mark Rutland
2020-03-10 17:28 ` Robin Murphy
2020-03-17 23:14 ` Will Deacon
2020-03-18 10:51 ` Mark Rutland
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=20200302181752.14251-1-mark.rutland@arm.com \
--to=mark.rutland@arm.com \
--cc=catalin.marinas@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=will@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).