From: Marc Zyngier <maz@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Hyunwoo Kim <imv4bel@gmail.com>, Joey Gouly <joey.gouly@arm.com>,
Oliver Upton <oupton@kernel.org>,
Wei-Lin Chang <weilin.chang@arm.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
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 #5
Date: Fri, 5 Jun 2026 17:45:16 +0100 [thread overview]
Message-ID: <20260605164516.2214533-1-maz@kernel.org> (raw)
Paolo,
Yes, I said that last week's pull request was the last. I really meant
it, honest. But people (and their AI best mate) keep finding ugly
stuff in dark corners, and I can't sit on this stuff much longer.
So here we have an assorted mess of bad races, broken userspace, and
architectural bugs. What's not to like? As usual, details in the tag
below.
Please pull,
M.
The following changes since commit 83726330748981372bde86ed5411d7b306612991:
KVM: arm64: Correctly cap ZCR_EL2 provided by a guest hypervisor (2026-05-29 10:04:00 +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-5
for you to fetch changes up to 17f073f78fc43280891ecde8f8ec3f84f98bb37c:
KVM: arm64: Correctly identify executable PTEs at stage-2 (2026-06-05 14:07:57 +0100)
----------------------------------------------------------------
KVM/arm64 fixes for 7.1, take #5
- Correctly drop the ITS translation cache reference when it actually
gets invalidated
- Take the SRCU lock for SW page table walks
- Restore POR_EL0 access to host EL0, avoiding POR_EL0 becoming
inaccessible from EL0 after running a guest
- Reassign nested_mmus array behind mmu_lock, ensuring that vcpu init
and MMU notifiers are mutually exclusive
- Correctly handle FEAT_XNX at stage-2
----------------------------------------------------------------
Hyunwoo Kim (3):
KVM: arm64: vgic-its: Drop the translation cache reference only for the erased entry
KVM: arm64: Take the SRCU lock for page table walks in fault injection and AT emulation
KVM: arm64: Reassign nested_mmus array behind mmu_lock
Joey Gouly (1):
KVM: arm64: Restore POR_EL0 access to host EL0
Oliver Upton (2):
KVM: arm64: nv: Fix handling of XN[0] when !FEAT_XNX
KVM: arm64: Correctly identify executable PTEs at stage-2
arch/arm64/include/asm/kvm_nested.h | 4 ++--
arch/arm64/kvm/at.c | 6 ++++--
arch/arm64/kvm/hyp/include/hyp/switch.h | 2 ++
arch/arm64/kvm/hyp/pgtable.c | 4 +++-
arch/arm64/kvm/nested.c | 33 ++++++++++++++++++++-------------
arch/arm64/kvm/vgic/vgic-its.c | 6 ++++--
6 files changed, 35 insertions(+), 20 deletions(-)
next reply other threads:[~2026-06-05 16:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 16:45 Marc Zyngier [this message]
2026-06-05 16:57 ` [GIT PULL] KVM/arm64 fixes for 7.1, take #5 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=20260605164516.2214533-1-maz@kernel.org \
--to=maz@kernel.org \
--cc=imv4bel@gmail.com \
--cc=joey.gouly@arm.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=oupton@kernel.org \
--cc=pbonzini@redhat.com \
--cc=seiden@linux.ibm.com \
--cc=suzuki.poulose@arm.com \
--cc=weilin.chang@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