From: Marc Zyngier <maz@kernel.org>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: kvmarm@lists.linux.dev, Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Mingwei Zhang <mizhang@google.com>,
Colton Lewis <coltonlewis@google.com>,
Raghavendra Rao Ananta <rananta@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Janne Grunau <j@jannau.net>
Subject: Re: [PATCH v3 00/14] KVM: arm64: FEAT_PMUv3 on Apple hardware
Date: Mon, 10 Mar 2025 13:13:21 +0000 [thread overview]
Message-ID: <86zfhtni4u.wl-maz@kernel.org> (raw)
In-Reply-To: <20250305202641.428114-1-oliver.upton@linux.dev>
On Wed, 05 Mar 2025 20:26:27 +0000,
Oliver Upton <oliver.upton@linux.dev> wrote:
>
> Hopefully close to the last spin, this time addressing Marc's comments
> on v2.
>
> Full details found in the v1 cover letter.
>
> v1: https://lore.kernel.org/kvmarm/20241217212048.3709204-1-oliver.upton@linux.dev/
> v2: https://lore.kernel.org/kvmarm/20250203183111.191519-1-oliver.upton@linux.dev/
>
> v2 -> v3:
> - Reorder and restructure patches to include map_pmuv3_event()
> definition w/ KVM usage.
> - Disallow events that lack a valid PMUv3 -> HW mapping
> - Various minor fixes/typos
>
> Oliver Upton (14):
> drivers/perf: apple_m1: Refactor event select/filter configuration
> drivers/perf: apple_m1: Support host/guest event filtering
> KVM: arm64: Compute PMCEID from arm_pmu's event bitmaps
> KVM: arm64: Always support SW_INCR PMU event
> KVM: arm64: Use a cpucap to determine if system supports FEAT_PMUv3
> KVM: arm64: Drop kvm_arm_pmu_available static key
> KVM: arm64: Use guard() to cleanup usage of arm_pmus_lock
> KVM: arm64: Move PMUVer filtering into KVM code
> KVM: arm64: Compute synthetic sysreg ESR for Apple PMUv3 traps
> KVM: arm64: Advertise PMUv3 if IMPDEF traps are present
> KVM: arm64: Remap PMUv3 events onto hardware
> drivers/perf: apple_m1: Provide helper for mapping PMUv3 events
> KVM: arm64: Provide 1 event counter on IMPDEF hardware
> arm64: Enable IMP DEF PMUv3 traps on Apple M*
>
> arch/arm64/include/asm/apple_m1_pmu.h | 1 +
> arch/arm64/include/asm/cpucaps.h | 2 +
> arch/arm64/include/asm/cpufeature.h | 28 +----
> arch/arm64/kernel/cpu_errata.c | 44 ++++++++
> arch/arm64/kernel/cpufeature.c | 28 +++++
> arch/arm64/kernel/image-vars.h | 5 -
> arch/arm64/kvm/arm.c | 4 +-
> arch/arm64/kvm/hyp/include/hyp/switch.h | 4 +-
> arch/arm64/kvm/hyp/vhe/switch.c | 22 ++++
> arch/arm64/kvm/pmu-emul.c | 138 +++++++++++++++++-------
> arch/arm64/kvm/pmu.c | 10 +-
> arch/arm64/tools/cpucaps | 2 +
> drivers/perf/apple_m1_cpu_pmu.c | 101 +++++++++++++----
> include/kvm/arm_pmu.h | 12 +--
> include/linux/perf/arm_pmu.h | 4 +
> 15 files changed, 301 insertions(+), 104 deletions(-)
>
>
> base-commit: 0ad2507d5d93f39619fc42372c347d6006b64319
I'm quite happy with the way this looks now (well, apart from patch
#9, but that's not something you can fix...).
Reviewed-by: Marc Zyngier <maz@kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-03-10 14:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 20:26 [PATCH v3 00/14] KVM: arm64: FEAT_PMUv3 on Apple hardware Oliver Upton
2025-03-05 20:26 ` [PATCH v3 01/14] drivers/perf: apple_m1: Refactor event select/filter configuration Oliver Upton
2025-03-05 20:26 ` [PATCH v3 02/14] drivers/perf: apple_m1: Support host/guest event filtering Oliver Upton
2025-03-05 20:26 ` [PATCH v3 03/14] KVM: arm64: Compute PMCEID from arm_pmu's event bitmaps Oliver Upton
2025-03-05 20:26 ` [PATCH v3 04/14] KVM: arm64: Always support SW_INCR PMU event Oliver Upton
2025-03-05 20:26 ` [PATCH v3 05/14] KVM: arm64: Use a cpucap to determine if system supports FEAT_PMUv3 Oliver Upton
2025-03-05 20:26 ` [PATCH v3 06/14] KVM: arm64: Drop kvm_arm_pmu_available static key Oliver Upton
2025-03-05 20:26 ` [PATCH v3 07/14] KVM: arm64: Use guard() to cleanup usage of arm_pmus_lock Oliver Upton
2025-03-05 20:26 ` [PATCH v3 08/14] KVM: arm64: Move PMUVer filtering into KVM code Oliver Upton
2025-03-05 20:26 ` [PATCH v3 09/14] KVM: arm64: Compute synthetic sysreg ESR for Apple PMUv3 traps Oliver Upton
2025-03-05 20:26 ` [PATCH v3 10/14] KVM: arm64: Advertise PMUv3 if IMPDEF traps are present Oliver Upton
2025-03-05 20:26 ` [PATCH v3 11/14] KVM: arm64: Remap PMUv3 events onto hardware Oliver Upton
2025-03-05 20:26 ` [PATCH v3 12/14] drivers/perf: apple_m1: Provide helper for mapping PMUv3 events Oliver Upton
2025-03-05 20:30 ` [PATCH v3 13/14] KVM: arm64: Provide 1 event counter on IMPDEF hardware Oliver Upton
2025-03-05 20:30 ` [PATCH v3 14/14] arm64: Enable IMP DEF PMUv3 traps on Apple M* Oliver Upton
2025-03-10 13:13 ` Marc Zyngier [this message]
2025-03-11 23:44 ` [PATCH v3 00/14] KVM: arm64: FEAT_PMUv3 on Apple hardware Oliver Upton
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=86zfhtni4u.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=coltonlewis@google.com \
--cc=j@jannau.net \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mizhang@google.com \
--cc=oliver.upton@linux.dev \
--cc=rananta@google.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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;
as well as URLs for NNTP newsgroup(s).