From: Joey Gouly <joey.gouly@arm.com>
To: Marc Zyngier <maz@kernel.org>
Cc: kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Oliver Upton <oliver.upton@linux.dev>,
Zenghui Yu <yuzenghui@huawei.com>
Subject: Re: [PATCH 0/2] KVM: arm64: EL2 PMU reset handling fixes
Date: Thu, 20 Feb 2025 10:44:19 +0000 [thread overview]
Message-ID: <20250220104419.GA2511466@e124191.cambridge.arm.com> (raw)
In-Reply-To: <20250217112412.3963324-1-maz@kernel.org>
On Mon, Feb 17, 2025 at 11:24:10AM +0000, Marc Zyngier wrote:
> Joey reports that some of his PMU tests do not behave quite as
> expected:
>
> - MDCR_EL2.HPMN is set to 0 out of reset
>
> - PMCR_EL0.P should reset all the counters when written from EL2
>
> These couple of patches attempt to remedy the situation. Note that
> they have only been compile-tested.
>
> Marc Zyngier (2):
> KVM: arm64: Fix MDCR_EL2.HPMN reset value
> KVM: arm64: Contextualise the handling of PMCR_EL0.P writes
>
> arch/arm64/kvm/pmu-emul.c | 21 ++++++++++++++++-----
> arch/arm64/kvm/sys_regs.c | 7 ++++++-
> 2 files changed, 22 insertions(+), 6 deletions(-)
I see you're discussing the API around this, but this does fix the PMU tests, so:
Tested-by: Joey Gouly <joey.gouly@arm.com>
prev parent reply other threads:[~2025-02-20 10:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 11:24 [PATCH 0/2] KVM: arm64: EL2 PMU reset handling fixes Marc Zyngier
2025-02-17 11:24 ` [PATCH 1/2] KVM: arm64: Fix MDCR_EL2.HPMN reset value Marc Zyngier
2025-02-17 18:53 ` Oliver Upton
2025-02-19 14:03 ` Marc Zyngier
2025-02-19 19:04 ` Oliver Upton
2025-02-19 21:10 ` Marc Zyngier
2025-02-17 11:24 ` [PATCH 2/2] KVM: arm64: Contextualise the handling of PMCR_EL0.P writes Marc Zyngier
2025-02-17 18:33 ` Oliver Upton
2025-02-20 10:44 ` Joey Gouly [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=20250220104419.GA2511466@e124191.cambridge.arm.com \
--to=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@arm.com \
--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