From: Marc Zyngier <maz@kernel.org>
To: kvmarm@lists.linux.dev, Colton Lewis <coltonlewis@google.com>
Cc: oupton@kernel.org, joey.gouly@arm.com, suzuki.poulose@arm.com,
yuzenghui@huawei.com, catalin.marinas@arm.com, will@kernel.org,
pbonzini@redhat.com, linux-arm-kernel@lists.infradead.org,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] KVM: arm64: Handle hidden FEAT_PMUv3 in ID_AA64DFR0_EL1
Date: Sat, 3 Oct 2026 13:14:00 +0100 [thread overview]
Message-ID: <179102963296.607377.2477246563507237480.b4-ty@b4> (raw)
In-Reply-To: <20260930211834.2773546-1-coltonlewis@google.com>
On Wed, 30 Sep 2026 21:18:32 +0000, Colton Lewis wrote:
> When userspace initializes a vCPU with KVM_ARM_VCPU_PMU_V3 and hides
> FEAT_PMUv3 via ID_AA64DFR0_EL1.PMUVer, KVM hits a WARN_ONCE("Unknown PMU
> version 0") during reset_pmevtyper() and continues to expose PMU system
> registers instead of emulating guest accesses as UNDEF.
>
> Patch 1 handles ID_AA64DFR0_EL1_PMUVer_NI in __kvm_pmu_event_mask() and
> removes the redundant kvm_vcpu_has_pmu() check in reset_pmevtyper().
> Patch 2 updates pmu_visibility() to check ID_AA64DFR0_EL1.PMUVer via
> kvm_has_feat() so PMU registers are marked REG_HIDDEN when FEAT_PMUv3 is
> not advertised.
>
> [...]
Applied to next, thanks!
[1/2] KVM: arm64: Handle ID_AA64DFR0_EL1.PMUVer == NI in __kvm_pmu_event_mask()
commit: aa41a7c3beb59f9dac4e60c9cf1d146f6c9025c4
[2/2] KVM: arm64: Check ID_AA64DFR0_EL1.PMUVer in pmu_visibility()
commit: 517cdec3d4b28ccf5dae2dd03dee2a0a1eef1981
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2026-10-03 12:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 21:18 [PATCH v2 0/2] KVM: arm64: Handle hidden FEAT_PMUv3 in ID_AA64DFR0_EL1 Colton Lewis
2026-09-30 21:18 ` [PATCH v2 1/2] KVM: arm64: Handle ID_AA64DFR0_EL1.PMUVer == NI in __kvm_pmu_event_mask() Colton Lewis
2026-09-30 21:18 ` [PATCH v2 2/2] KVM: arm64: Check ID_AA64DFR0_EL1.PMUVer in pmu_visibility() Colton Lewis
2026-10-03 12:14 ` Marc Zyngier [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=179102963296.607377.2477246563507237480.b4-ty@b4 \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=coltonlewis@google.com \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oupton@kernel.org \
--cc=pbonzini@redhat.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