From: Marc Zyngier <maz@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Mark Brown <broonie@kernel.org>,
Qiang Ma <maqianga@uniontech.com>,
Vincent Donnefort <vdonnefort@google.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Joey Gouly <joey.gouly@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Oliver Upton <oupton@kernel.org>,
Zenghui Yu <yuzenghui@huawei.com>,
kvmarm@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
kvm@vger.kernel.org
Subject: [GIT PULL] KVM/arm64 fixes for 7.1, take #4
Date: Fri, 29 May 2026 11:54:05 +0100 [thread overview]
Message-ID: <20260529105405.1839362-1-maz@kernel.org> (raw)
Paolo,
This is hopefully the last round of fixes for 7.1 on the KVM/arm64
front.
We have yet another batch of fixes for the newly introduced tracing
code (memory leaks), a fix for a config symbol misspelled in the
source code (therefore being permanently disabled), a fix for an
embarrassing bug in the PMU emulation (write any value as long as it
is zero), and an SVE sanitisation bug in nested virt resulting in a
guest being able to access more than it really should.
I've purposely refrained from adding another lot of fixes for more
benign issues since His Majesty has announced he'd be picky about
that. Fear not, they'll be in the 7.2 pull request.
Please pull,
M.
The following changes since commit 1702da76e017ae0fbe1a92b07bc332972c293e89:
KVM: arm64: Fix nVHE/pKVM hyp tracing error on invalid desc (2026-05-20 08:08:37 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvmarm-fixes-7.1-4
for you to fetch changes up to 83726330748981372bde86ed5411d7b306612991:
KVM: arm64: Correctly cap ZCR_EL2 provided by a guest hypervisor (2026-05-29 10:04:00 +0100)
----------------------------------------------------------------
KVM/arm64 fixes for 7.1, take #4
- Restore CONFIG_PKVM_DISABLE_STAGE2_ON_PANIC to its former glory by
making sure the config symbol is correctly spelled out in the code
- Don't reset the AArch32 view of the PMU counters to zero when the
guest is writing to them
- Fix an assorted collection of memory leaks in the newly added tracing
code
- Fix the capping of ZCR_EL2 which could be used in an unsanitised way
by an L2 guest
----------------------------------------------------------------
Mark Brown (1):
KVM: arm64: Correctly cap ZCR_EL2 provided by a guest hypervisor
Qiang Ma (1):
KVM: arm64: PMU: Preserve AArch32 counter low bits
Vincent Donnefort (4):
KVM: arm64: Fix CONFIG_PKVM_DISABLE_STAGE2_ON_PANIC
KVM: arm64: Fix meta-page unsharing in pKVM hyp tracing
KVM: arm64: Fix rollback in hyp_trace_buffer_share_hyp()
KVM: arm64: Fix memory leak in hyp_trace_unload()
arch/arm64/include/asm/kvm_host.h | 2 +-
arch/arm64/kvm/hyp/include/hyp/switch.h | 16 ++++++++++------
arch/arm64/kvm/hyp/nvhe/host.S | 2 +-
arch/arm64/kvm/hyp_trace.c | 9 ++++++---
arch/arm64/kvm/nested.c | 5 +++++
arch/arm64/kvm/pmu-emul.c | 4 ++--
arch/arm64/kvm/sys_regs.c | 11 +++--------
7 files changed, 28 insertions(+), 21 deletions(-)
next reply other threads:[~2026-05-29 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 10:54 Marc Zyngier [this message]
2026-05-29 17:31 ` [GIT PULL] KVM/arm64 fixes for 7.1, take #4 Paolo Bonzini
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=20260529105405.1839362-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=broonie@kernel.org \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maqianga@uniontech.com \
--cc=oupton@kernel.org \
--cc=pbonzini@redhat.com \
--cc=seiden@linux.ibm.com \
--cc=suzuki.poulose@arm.com \
--cc=vdonnefort@google.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