Paolo,
Here's the third (and hopefully final) set of fixes for 5.18. Two
rather simple patches: one addressing a userspace-visible change in
behaviour with GICv3, and a fix for pKVM in combination with CPUs
affected by Spectre-v3a.
Please pull,
M.
The following changes since commit 85ea6b1ec915c9dd90caf3674b203999d8c7e062:
KVM: arm64: Inject exception on out-of-IPA-range translation fault (2022-04-27 23:02:23 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvmarm-fixes-5.18-3
for you to fetch changes up to 2e40316753ee552fb598e8da8ca0d20a04e67453:
KVM: arm64: Don't hypercall before EL2 init (2022-05-15 12:14:14 +0100)
----------------------------------------------------------------
KVM/arm64 fixes for 5.18, take #3
- Correctly expose GICv3 support even if no irqchip is created
so that userspace doesn't observe it changing pointlessly
(fixing a regression with QEMU)
- Don't issue a hypercall to set the id-mapped vectors when
protected mode is enabled
----------------------------------------------------------------
Marc Zyngier (1):
KVM: arm64: vgic-v3: Consistently populate ID_AA64PFR0_EL1.GIC
Quentin Perret (1):
KVM: arm64: Don't hypercall before EL2 init
arch/arm64/kvm/arm.c | 3 ++-
arch/arm64/kvm/sys_regs.c | 3 +--
2 files changed, 3 insertions(+), 3 deletions(-)
_______________________________________________
kvmarm mailing list
kvmarm@xxxxxxxxxxxxxxxxxxxxx
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
