From: Oliver Upton <oupton@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Marc Zyngier <maz@kernel.org>,
kvm@vger.kernel.org, kvmarm@lists.linux.dev
Subject: KVM/arm64 fixes for 6.19
Date: Thu, 15 Jan 2026 01:30:25 -0800 [thread overview]
Message-ID: <aWizsSzD3fRWMsAc@kernel.org> (raw)
Hi Paolo,
Here is the first (and likely only) set of fixes for 6.19. Small batch
of changes fixing issues in non-standard configurations like pKVM, hVHE,
and nested.
Details are in the tag, please pull.
Thanks,
Oliver
The following changes since commit f8f9c1f4d0c7a64600e2ca312dec824a0bc2f1da:
Linux 6.19-rc3 (2025-12-28 13:24:26 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git/ tags/kvmarm-fixes-6.19-1
for you to fetch changes up to 19cffd16ed6489770272ba383ff3aaec077e01ed:
KVM: arm64: Invert KVM_PGTABLE_WALK_HANDLE_FAULT to fix pKVM walkers (2026-01-10 02:19:52 -0800)
----------------------------------------------------------------
KVM/arm64 fixes for 6.19
- Ensure early return semantics are preserved for pKVM fault handlers
- Fix case where the kernel runs with the guest's PAN value when
CONFIG_ARM64_PAN is not set
- Make stage-1 walks to set the access flag respect the access
permission of the underlying stage-2, when enabled
- Propagate computed FGT values to the pKVM view of the vCPU at
vcpu_load()
- Correctly program PXN and UXN privilege bits for hVHE's stage-1 page
tables
- Check that the VM is actually using VGICv3 before accessing the GICv3
CPU interface
- Delete some unused code
----------------------------------------------------------------
Alexandru Elisei (4):
KVM: arm64: Copy FGT traps to unprotected pKVM VCPU on VCPU load
KVM: arm64: Inject UNDEF for a register trap without accessor
KVM: arm64: Remove extra argument for __pvkm_host_{share,unshare}_hyp()
KVM: arm64: Remove unused parameter in synchronize_vcpu_pstate()
Dongxu Sun (1):
KVM: arm64: Remove unused vcpu_{clear,set}_wfx_traps()
Marc Zyngier (2):
KVM: arm64: Fix EL2 S1 XN handling for hVHE setups
KVM: arm64: Don't blindly set set PSTATE.PAN on guest exit
Oliver Upton (1):
KVM: arm64: nv: Respect stage-2 write permssion when setting stage-1 AF
Sascha Bischoff (1):
KVM: arm64: gic: Check for vGICv3 when clearing TWI
Will Deacon (1):
KVM: arm64: Invert KVM_PGTABLE_WALK_HANDLE_FAULT to fix pKVM walkers
arch/arm64/include/asm/kvm_asm.h | 2 ++
arch/arm64/include/asm/kvm_emulate.h | 16 ----------------
arch/arm64/include/asm/kvm_pgtable.h | 16 ++++++++++++----
arch/arm64/include/asm/sysreg.h | 3 ++-
arch/arm64/kernel/image-vars.h | 1 +
arch/arm64/kvm/arm.c | 1 +
arch/arm64/kvm/at.c | 8 ++++++--
arch/arm64/kvm/hyp/entry.S | 4 +++-
arch/arm64/kvm/hyp/include/hyp/switch.h | 2 +-
arch/arm64/kvm/hyp/nvhe/hyp-main.c | 3 +++
arch/arm64/kvm/hyp/nvhe/pkvm.c | 1 -
arch/arm64/kvm/hyp/nvhe/switch.c | 2 +-
arch/arm64/kvm/hyp/pgtable.c | 5 +++--
arch/arm64/kvm/hyp/vhe/switch.c | 2 +-
arch/arm64/kvm/mmu.c | 12 +++++-------
arch/arm64/kvm/sys_regs.c | 5 ++++-
arch/arm64/kvm/va_layout.c | 28 ++++++++++++++++++++++++++++
17 files changed, 73 insertions(+), 38 deletions(-)
next reply other threads:[~2026-01-15 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 9:30 Oliver Upton [this message]
2026-01-15 10:04 ` KVM/arm64 fixes for 6.19 Marc Zyngier
2026-01-24 7:46 ` 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=aWizsSzD3fRWMsAc@kernel.org \
--to=oupton@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.