KVM/arm64 fixes for 5.10, take #1
Subsystems (4)
Marc Zyngier
maintainer[Apologies for the spam, I appear to have forgotten to Cc the lists in
my initial posting]
Hi Paolo,
It was good to see you (and everyone else) at KVM Forum this week!
And to celebrate, here's a first batch of fixes for KVM/arm64. A bunch of them are addressing issues introduced by the invasive changes that took place in the 5.10 merge window (MM, nVHE host entry). A few others are addressing some older bugs (VFIO PTE mappings, AArch32 debug, composite huge pages), and a couple of improvements (HYP-visible capabilities are made more robust).
Please pull,
M.
The following changes since commit 4e5dc64c43192b4fd4c96ac150a8f013065f5f5b:
Merge branches 'kvm-arm64/pt-new' and 'kvm-arm64/pmu-5.9' into kvmarm-master/next (2020-10-02 09:25:55 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kvmarm/kvmarm.git tags/kvmarm-fixes-5.10-1
for you to fetch changes up to 22f553842b14a1289c088a79a67fb479d3fa2a4e:
KVM: arm64: Handle Asymmetric AArch32 systems (2020-10-30 16:06:22 +0000)
----------------------------------------------------------------
KVM/arm64 fixes for 5.10, take #1
- Force PTE mapping on device pages provided via VFIO
- Fix detection of cacheable mapping at S2
- Fallback to PMD/PTE mappings for composite huge pages
- Fix accounting of Stage-2 PGD allocation
- Fix AArch32 handling of some of the debug registers
- Simplify host HYP entry
- Fix stray pointer conversion on nVHE TLB invalidation
- Fix initialization of the nVHE code
- Simplify handling of capabilities exposed to HYP
- Nuke VCPUs caught using a forbidden AArch32 EL0
----------------------------------------------------------------
Gavin Shan (1):
KVM: arm64: Use fallback mapping sizes for contiguous huge page sizes
Marc Zyngier (4):
KVM: arm64: Don't corrupt tpidr_el2 on failed HVC call
KVM: arm64: Remove leftover kern_hyp_va() in nVHE TLB invalidation
KVM: arm64: Drop useless PAN setting on host EL1 to EL2 transition
KVM: arm64: Fix AArch32 handling of DBGD{CCINT,SCRext} and DBGVCR
Mark Rutland (3):
KVM: arm64: Factor out is_{vhe,nvhe}_hyp_code()
arm64: cpufeature: reorder cpus_have_{const, final}_cap()
arm64: cpufeature: upgrade hyp caps to final
Qais Yousef (1):
KVM: arm64: Handle Asymmetric AArch32 systems
Santosh Shukla (1):
KVM: arm64: Force PTE mapping on fault resulting in a device mapping
Will Deacon (2):
KVM: arm64: Allocate stage-2 pgd pages with GFP_KERNEL_ACCOUNT
KVM: arm64: Fix masks in stage2_pte_cacheable()
arch/arm64/include/asm/cpufeature.h | 40 ++++++++++++++++++++++++++++--------- arch/arm64/include/asm/kvm_host.h | 1 + arch/arm64/include/asm/virt.h | 9 ++++----- arch/arm64/kernel/image-vars.h | 1 - arch/arm64/kvm/arm.c | 19 ++++++++++++++++++ arch/arm64/kvm/hyp/nvhe/host.S | 2 -- arch/arm64/kvm/hyp/nvhe/hyp-init.S | 23 ++++++++++++++------- arch/arm64/kvm/hyp/nvhe/tlb.c | 1 - arch/arm64/kvm/hyp/pgtable.c | 4 ++-- arch/arm64/kvm/mmu.c | 27 ++++++++++++++++++------- arch/arm64/kvm/sys_regs.c | 6 +++--- 11 files changed, 96 insertions(+), 37 deletions(-)
Marc Zyngier
maintainerPATCH 1/12 KVM: arm64: Don't corrupt tpidr_el2 on failed HVC call
The hyp-init code starts by stashing a register in TPIDR_EL2 in in order to free a register. This happens no matter if the HVC call is legal or not.
Although nothing wrong seems to come out of it, it feels odd to alter the EL2 state for something that eventually returns an error.
Instead, use the fact that we know exactly which bits of the __kvm_hyp_init call are non-zero to perform the check with a series of EOR/ROR instructions, combined with a build-time check that the value is the one we expect.
--- arch/arm64/kvm/hyp/nvhe/hyp-init.S | 23 ++++++++++++++++------- 1 file changed, 16 insertions(+), 7 deletions(-)
arch/arm64/kvm/hyp/nvhe/hyp-init.S +16 -7
@@ -57,16 +57,25 @@ __do_hyp_init: cmp x0, #HVC_STUB_HCALL_NR b.lo __kvm_handle_stub_hvc - /* Set tpidr_el2 for use by HYP to free a register */ - msr tpidr_el2, x2 - - mov x2, #KVM_HOST_SMCCC_FUNC(__kvm_hyp_init) - cmp x0, x2 - b.eq 1f + // We only actively check bits [24:31], and everything + // else has to be zero, which we check at build time. +#if (KVM_HOST_SMCCC_FUNC(__kvm_hyp_init) & 0xFFFFFFFF00FFFFFF) +#error Unexpected __KVM_HOST_SMCCC_FUNC___kvm_hyp_init value +#endif + + ror x0, x0, #24 + eor x0, x0, #((KVM_HOST_SMCCC_FUNC(__kvm_hyp_init) >> 24) & 0xF) + ror x0, x0, #4 + eor x0, x0, #((KVM_HOST_SMCCC_FUNC(__kvm_hyp_init) >> 28) & 0xF) + cbz x0, 1f mov x0, #SMCCC_RET_NOT_SUPPORTED eret -1: phys_to_ttbr x0, x1 +1: + /* Set tpidr_el2 for use by HYP to free a register */ + msr tpidr_el2, x2 + + phys_to_ttbr x0, x1 alternative_if ARM64_HAS_CNP orr x0, x0, #TTBR_CNP_BIT alternative_else_nop_endif
Signature · 1 line
2.28.0
Marc Zyngier
maintainerPATCH 2/12 KVM: arm64: Remove leftover kern_hyp_va() in nVHE TLB invalidation
In reply to Marc ZyngierThe new calling convention says that pointers coming from the SMCCC interface are turned into their HYP version in the host HVC handler. However, there is still a stray kern_hyp_va() in the TLB invalidation code, which could result in a corrupted pointer.
Drop the spurious conversion.
--- arch/arm64/kvm/hyp/nvhe/tlb.c | 1 - 1 file changed, 1 deletion(-)
arch/arm64/kvm/hyp/nvhe/tlb.c +0 -1
@@ -121,7 +121,6 @@ void __kvm_tlb_flush_local_vmid(struct kvm_s2_mmu *mmu)struct tlb_inv_context cxt;/* Switch to requested VMID */ - mmu =kern_hyp_va (mmu);__tlb_switch_to_guest (mmu, &cxt);__tlbi (vmalle1);
Signature · 1 line
2.28.0
Marc Zyngier
maintainerPATCH 3/12 KVM: arm64: Drop useless PAN setting on host EL1 to EL2 transition
In reply to Marc ZyngierSetting PSTATE.PAN when entering EL2 on nVHE doesn't make much sense as this bit only means something for translation regimes that include EL0. This obviously isn't the case in the nVHE case, so let's drop this setting.
--- arch/arm64/kvm/hyp/nvhe/host.S | 2 -- 1 file changed, 2 deletions(-)
arch/arm64/kvm/hyp/nvhe/host.S +0 -2
@@ -17,8 +17,6 @@ SYM_FUNC_START(__host_exit) get_host_ctxt x0, x1 - ALTERNATIVE(nop, SET_PSTATE_PAN(1), ARM64_HAS_PAN, CONFIG_ARM64_PAN) - /* Store the host regs x2 and x3 */ stp x2, x3, [x0, #CPU_XREG_OFFSET(2)]
Signature · 1 line
2.28.0
Marc Zyngier
maintainerPATCH 4/12 KVM: arm64: Allocate stage-2 pgd pages with GFP_KERNEL_ACCOUNT
In reply to Marc ZyngierFrom: Will Deacon <[email protected]>
For consistency with the rest of the stage-2 page-table page allocations (performing using a kvm_mmu_memory_cache), ensure that __GFP_ACCOUNT is included in the GFP flags for the PGD pages.
--- arch/arm64/kvm/hyp/pgtable.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/kvm/hyp/pgtable.c +1 -1
@@ -846,7 +846,7 @@ int kvm_pgtable_stage2_init(struct kvm_pgtable *pgt, struct kvm *kvm)u32 start_level =VTCR_EL2_TGRAN_SL0_BASE - sl0; pgd_sz =kvm_pgd_pages (ia_bits, start_level) *PAGE_SIZE ; - pgt->pgd =alloc_pages_exact (pgd_sz,GFP_KERNEL | __GFP_ZERO); + pgt->pgd =alloc_pages_exact (pgd_sz,GFP_KERNEL_ACCOUNT | __GFP_ZERO);if (!pgt->pgd)return -ENOMEM ;
Signature · 1 line
2.28.0
Marc Zyngier
maintainerPATCH 5/12 KVM: arm64: Fix AArch32 handling of DBGD{CCINT,SCRext} and DBGVCR
In reply to Marc ZyngierThe DBGD{CCINT,SCRext} and DBGVCR register entries in the cp14 array are missing their target register, resulting in all accesses being targetted at the guard sysreg (indexed by __INVALID_SYSREG__).
Point the emulation code at the actual register entries.
--- arch/arm64/include/asm/kvm_host.h | 1 + arch/arm64/kvm/sys_regs.c | 6 +++--- 2 files changed, 4 insertions(+), 3 deletions(-)
arch/arm64/include/asm/kvm_host.h +1 -0
@@ -239,6 +239,7 @@ enum vcpu_sysreg {#define cp14_DBGWCR0 (DBGWCR0_EL1 * 2)#define cp14_DBGWVR0 (DBGWVR0_EL1 * 2)#define cp14_DBGDCCINT (MDCCINT_EL1 * 2) +#define cp14_DBGVCR (DBGVCR32_EL2 * 2)#define NR_COPRO_REGS (NR_SYS_REGS * 2)
arch/arm64/kvm/sys_regs.c +3 -3
@@ -1881,9 +1881,9 @@ static const struct sys_reg_desc cp14_regs[] = { { Op1( 0), CRn( 0), CRm( 1), Op2( 0), trap_raz_wi },DBG_BCR_BVR_WCR_WVR (1 ),/* DBGDCCINT */ - { Op1( 0), CRn( 0), CRm( 2), Op2( 0), trap_debug32 }, + { Op1( 0), CRn( 0), CRm( 2), Op2( 0), trap_debug32, NULL, cp14_DBGDCCINT },/* DBGDSCRext */ - { Op1( 0), CRn( 0), CRm( 2), Op2( 2), trap_debug32 }, + { Op1( 0), CRn( 0), CRm( 2), Op2( 2), trap_debug32, NULL, cp14_DBGDSCRext },DBG_BCR_BVR_WCR_WVR (2 ),/* DBGDTR[RT]Xint */ { Op1( 0), CRn( 0), CRm( 3), Op2( 0), trap_raz_wi },
@@ -1898,7 +1898,7 @@ static const struct sys_reg_desc cp14_regs[] = { { Op1( 0), CRn( 0), CRm( 6), Op2( 2), trap_raz_wi },DBG_BCR_BVR_WCR_WVR (6 ),/* DBGVCR */ - { Op1( 0), CRn( 0), CRm( 7), Op2( 0), trap_debug32 }, + { Op1( 0), CRn( 0), CRm( 7), Op2( 0), trap_debug32, NULL, cp14_DBGVCR },DBG_BCR_BVR_WCR_WVR (7 ),DBG_BCR_BVR_WCR_WVR (8 ), DBG_BCR_BVR_WCR_WVR(9),
Signature · 1 line
2.28.0
Marc Zyngier
maintainerPATCH 6/12 KVM: arm64: Fix masks in stage2_pte_cacheable()
In reply to Marc ZyngierFrom: Will Deacon <[email protected]>
stage2_pte_cacheable() tries to figure out whether the mapping installed in its 'pte' parameter is cacheable or not. Unfortunately, it fails miserably because it extracts the memory attributes from the entry using FIELD_GET(), which returns the attributes shifted down to bit 0, but then compares this with the unshifted value generated by the PAGE_S2_MEMATTR() macro.
A direct consequence of this bug is that cache maintenance is silently skipped, which in turn causes 32-bit guests to crash early on when their set/way maintenance is trapped but not emulated correctly.
Fix the broken masks by avoiding the use of FIELD_GET() altogether.
--- arch/arm64/kvm/hyp/pgtable.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm64/kvm/hyp/pgtable.c +1 -1
@@ -635,7 +635,7 @@ static void stage2_flush_dcache(void *addr, u64 size)static bool stage2_pte_cacheable (kvm_pte_t pte) { -u64 memattr =FIELD_GET (KVM_PTE_LEAF_ATTR_LO_S2_MEMATTR , pte); +u64 memattr = pte &KVM_PTE_LEAF_ATTR_LO_S2_MEMATTR ;return memattr ==PAGE_S2_MEMATTR (NORMAL ); }
Signature · 1 line
2.28.0
Marc Zyngier
maintainerPATCH 7/12 KVM: arm64: Use fallback mapping sizes for contiguous huge page sizes
In reply to Marc ZyngierFrom: Gavin Shan <[email protected]>
Although huge pages can be created out of multiple contiguous PMDs or PTEs, the corresponding sizes are not supported at Stage-2 yet.
Instead of failing the mapping, fall back to the nearer supported mapping size (CONT_PMD to PMD and CONT_PTE to PTE respectively).
--- arch/arm64/kvm/mmu.c | 26 +++++++++++++++++++------- 1 file changed, 19 insertions(+), 7 deletions(-)
arch/arm64/kvm/mmu.c +19 -7
@@ -787,14 +787,26 @@ static int user_mem_abort(struct kvm_vcpu *vcpu, phys_addr_t fault_ipa, vma_shift =PAGE_SHIFT ; } -if (vma_shift ==PUD_SHIFT && - !fault_supports_stage2_huge_mapping (memslot, hva,PUD_SIZE )) - vma_shift =PMD_SHIFT ; - -if (vma_shift ==PMD_SHIFT && - !fault_supports_stage2_huge_mapping (memslot, hva,PMD_SIZE )) { - force_pte = true; +switch (vma_shift) { +case PUD_SHIFT : +if (fault_supports_stage2_huge_mapping (memslot, hva,PUD_SIZE )) +break ; + fallthrough; +case CONT_PMD_SHIFT : + vma_shift =PMD_SHIFT ; + fallthrough; +case PMD_SHIFT : +if (fault_supports_stage2_huge_mapping (memslot, hva,PMD_SIZE )) +break ; + fallthrough; +case CONT_PTE_SHIFT : vma_shift =PAGE_SHIFT ; + force_pte = true; + fallthrough; +case PAGE_SHIFT : +break ; +default : +WARN_ONCE (1 ,"Unknown vma_shift %d" , vma_shift); } vma_pagesize =1UL << vma_shift;
Signature · 1 line
2.28.0
Marc Zyngier
maintainerPATCH 8/12 KVM: arm64: Force PTE mapping on fault resulting in a device mapping
In reply to Marc ZyngierFrom: Santosh Shukla <[email protected]>
VFIO allows a device driver to resolve a fault by mapping a MMIO range. This can be subsequently result in user_mem_abort() to try and compute a huge mapping based on the MMIO pfn, which is a sure recipe for things to go wrong.
Instead, force a PTE mapping when the pfn faulted in has a device mapping.
--- arch/arm64/kvm/mmu.c | 1 + 1 file changed, 1 insertion(+)
arch/arm64/kvm/mmu.c +1 -0
@@ -851,6 +851,7 @@ static int user_mem_abort(struct kvm_vcpu *vcpu, phys_addr_t fault_ipa,if (kvm_is_device_pfn (pfn)) { device = true; + force_pte = true; }else if (logging_active && !write_fault) {/* * Only actually map the page as writable if this was a write
Signature · 1 line
2.28.0
Marc Zyngier
maintainerPATCH 9/12 KVM: arm64: Factor out is_{vhe,nvhe}_hyp_code()
In reply to Marc ZyngierFrom: Mark Rutland <[email protected]>
Currently has_vhe() detects whether it is being compiled for VHE/NVHE hyp code based on preprocessor definitions, and uses this knowledge to avoid redundant runtime checks.
There are other cases where we'd like to use this knowledge, so let's factor the preprocessor checks out into separate helpers.
There should be no functional change as a result of this patch.
--- arch/arm64/include/asm/virt.h | 21 ++++++++++++++++----- 1 file changed, 16 insertions(+), 5 deletions(-)
arch/arm64/include/asm/virt.h +16 -5
@@ -83,16 +83,27 @@ static inline bool is_kernel_in_hyp_mode(void)return read_sysreg (CurrentEL) == CurrentEL_EL2; } +static __always_inline bool is_vhe_hyp_code(void) +{ +/* Only defined for code run in VHE hyp context */ +return __is_defined (__KVM_VHE_HYPERVISOR__); +} + +static __always_inline bool is_nvhe_hyp_code(void) +{ +/* Only defined for code run in NVHE hyp context */ +return __is_defined (__KVM_NVHE_HYPERVISOR__); +} + static __always_inline bool has_vhe(void) {/* -* The following macros are defined for code specic to VHE/nVHE. -* If has_vhe() is inlined into those compilation units, it can -* be determined statically. Otherwise fall back to caps. +* Code only run in VHE/NVHE hyp context can assume VHE is present or +* absent. Otherwise fall back to caps. */ -if (__is_defined (__KVM_VHE_HYPERVISOR__)) +if (is_vhe_hyp_code ())return true; -else if (__is_defined (__KVM_NVHE_HYPERVISOR__)) +else if (is_nvhe_hyp_code ())return false;else return cpus_have_final_cap (ARM64_HAS_VIRT_HOST_EXTN );
Signature · 1 line
2.28.0
Marc Zyngier
maintainerPATCH 10/12 arm64: cpufeature: reorder cpus_have_{const, final}_cap()
In reply to Marc ZyngierFrom: Mark Rutland <[email protected]>
In a subsequent patch we'll modify cpus_have_const_cap() to call cpus_have_final_cap(), and hence we need to define cpus_have_final_cap() first.
To make subsequent changes easier to follow, this patch reorders the two without making any other changes.
There should be no functional change as a result of this patch.
--- arch/arm64/include/asm/cpufeature.h | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-)
arch/arm64/include/asm/cpufeature.h +8 -8
@@ -428,35 +428,35 @@ static __always_inline bool __cpus_have_const_cap(int num) }/* -* Test for a capability, possibly with a runtime check. +* Test for a capability without a runtime check. * -* Before capabilities are finalized, this behaves as cpus_have_cap(). +* Before capabilities are finalized, this will BUG(). * After capabilities are finalized, this is patched to avoid a runtime check. * * @num must be a compile-time constant. */ -static __always_inline bool cpus_have_const_cap(int num) +static __always_inline bool cpus_have_final_cap(int num) {if (system_capabilities_finalized ())return __cpus_have_const_cap (num);else -return cpus_have_cap (num); +BUG (); }/* -* Test for a capability without a runtime check. +* Test for a capability, possibly with a runtime check. * -* Before capabilities are finalized, this will BUG(). +* Before capabilities are finalized, this behaves as cpus_have_cap(). * After capabilities are finalized, this is patched to avoid a runtime check. * * @num must be a compile-time constant. */ -static __always_inline bool cpus_have_final_cap(int num) +static __always_inline bool cpus_have_const_cap(int num) {if (system_capabilities_finalized ())return __cpus_have_const_cap (num);else -BUG (); +return cpus_have_cap (num); }static inline void cpus_set_cap (unsigned int num)
Signature · 1 line
2.28.0
Marc Zyngier
maintainerPATCH 11/12 arm64: cpufeature: upgrade hyp caps to final
In reply to Marc ZyngierFrom: Mark Rutland <[email protected]>
We finalize caps before initializing kvm hyp code, and any use of cpus_have_const_cap() in kvm hyp code generates redundant and potentially unsound code to read the cpu_hwcaps array.
A number of helper functions used in both hyp context and regular kernel context use cpus_have_const_cap(), as some regular kernel code runs before the capabilities are finalized. It's tedious and error-prone to write separate copies of these for hyp and non-hyp code.
So that we can avoid the redundant code, let's automatically upgrade cpus_have_const_cap() to cpus_have_final_cap() when used in hyp context. With this change, there's never a reason to access to cpu_hwcaps array from hyp code, and we don't need to create an NVHE alias for this.
This should have no effect on non-hyp code.
--- arch/arm64/include/asm/cpufeature.h | 26 ++++++++++++++++++++++++-- arch/arm64/include/asm/virt.h | 12 ------------ arch/arm64/kernel/image-vars.h | 1 - 3 files changed, 24 insertions(+), 15 deletions(-)
arch/arm64/include/asm/cpufeature.h +24 -2
@@ -375,6 +375,23 @@ cpucap_multi_entry_cap_matches(const struct arm64_cpu_capabilities *entry,return false; } +static __always_inline bool is_vhe_hyp_code(void) +{ +/* Only defined for code run in VHE hyp context */ +return __is_defined (__KVM_VHE_HYPERVISOR__); +} + +static __always_inline bool is_nvhe_hyp_code(void) +{ +/* Only defined for code run in NVHE hyp context */ +return __is_defined (__KVM_NVHE_HYPERVISOR__); +} + +static __always_inline bool is_hyp_code(void) +{ +return is_vhe_hyp_code () ||is_nvhe_hyp_code (); +} + extern DECLARE_BITMAP(cpu_hwcaps, ARM64_NCAPS);extern struct static_key_false cpu_hwcap_keys[ARM64_NCAPS ];extern struct static_key_false arm64_const_caps_ready;
@@ -444,8 +461,11 @@ static __always_inline bool cpus_have_final_cap(int num) }/* -* Test for a capability, possibly with a runtime check. +* Test for a capability, possibly with a runtime check for non-hyp code. * +* For hyp code, this behaves the same as cpus_have_final_cap(). +* +* For non-hyp code: * Before capabilities are finalized, this behaves as cpus_have_cap(). * After capabilities are finalized, this is patched to avoid a runtime check. *
@@ -453,7 +473,9 @@ static __always_inline bool cpus_have_final_cap(int num)*/ static __always_inline bool cpus_have_const_cap(int num) { -if (system_capabilities_finalized ()) +if (is_hyp_code ()) +return cpus_have_final_cap (num); +else if (system_capabilities_finalized ())return __cpus_have_const_cap (num);else return cpus_have_cap (num);
arch/arm64/include/asm/virt.h +0 -12
@@ -83,18 +83,6 @@ static inline bool is_kernel_in_hyp_mode(void)return read_sysreg (CurrentEL) == CurrentEL_EL2; } -static __always_inline bool is_vhe_hyp_code(void) -{ -/* Only defined for code run in VHE hyp context */ -return __is_defined (__KVM_VHE_HYPERVISOR__); -} - -static __always_inline bool is_nvhe_hyp_code(void) -{ -/* Only defined for code run in NVHE hyp context */ -return __is_defined (__KVM_NVHE_HYPERVISOR__); -} - static __always_inline bool has_vhe(void) {/*
arch/arm64/kernel/image-vars.h +0 -1
@@ -87,7 +87,6 @@ KVM_NVHE_ALIAS(__icache_flags);/* Kernel symbols needed for cpus_have_final/const_caps checks. */ KVM_NVHE_ALIAS (arm64_const_caps_ready);KVM_NVHE_ALIAS (cpu_hwcap_keys); -KVM_NVHE_ALIAS (cpu_hwcaps);/* Static keys which are set if a vGIC trap should be handled in hyp. */ KVM_NVHE_ALIAS (vgic_v2_cpuif_trap);
Signature · 1 line
2.28.0
Marc Zyngier
maintainerPATCH 12/12 KVM: arm64: Handle Asymmetric AArch32 systems
In reply to Marc ZyngierFrom: Qais Yousef <[email protected]>
On a system without uniform support for AArch32 at EL0, it is possible for the guest to force run AArch32 at EL0 and potentially cause an illegal exception if running on a core without AArch32. Add an extra check so that if we catch the guest doing that, then we prevent it from running again by resetting vcpu->arch.target and return ARM_EXCEPTION_IL.
We try to catch this misbehaviour as early as possible and not rely on an illegal exception occuring to signal the problem. Attempting to run a 32bit app in the guest will produce an error from QEMU if the guest exits while running in AArch32 EL0.
Tested on Juno by instrumenting the host to fake asym aarch32 and instrumenting KVM to make the asymmetry visible to the guest.
[will: Incorporated feedback from Marc]
--- arch/arm64/kvm/arm.c | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+)
arch/arm64/kvm/arm.c +19 -0
@@ -808,6 +808,25 @@ int kvm_arch_vcpu_ioctl_run(struct kvm_vcpu *vcpu)preempt_enable (); +/* +* The ARMv8 architecture doesn't give the hypervisor +* a mechanism to prevent a guest from dropping to AArch32 EL0 +* if implemented by the CPU. If we spot the guest in such +* state and that we decided it wasn't supposed to do so (like +* with the asymmetric AArch32 case), return to userspace with +* a fatal error. +*/ +if (!system_supports_32bit_el0 () &&vcpu_mode_is_32bit (vcpu)) { +/* +* As we have caught the guest red-handed, decide that +* it isn't fit for purpose anymore by making the vcpu +* invalid. The VMM can try and fix it by issuing a +* KVM_ARM_VCPU_INIT if it really wants to. +*/ + vcpu->arch.target =-1 ; + ret =ARM_EXCEPTION_IL ; + } + ret =handle_exit (vcpu, ret); }
Signature · 1 line
2.28.0
Paolo Bonzini
maintainerQuoted 10 lines · Marc Zyngier
Hi Paolo,
It was good to see you (and everyone else) at KVM Forum this week!
And to celebrate, here's a first batch of fixes for KVM/arm64. A bunch of them are addressing issues introduced by the invasive changes that took place in the 5.10 merge window (MM, nVHE host entry). A few others are addressing some older bugs (VFIO PTE mappings, AArch32 debug, composite huge pages), and a couple of improvements (HYP-visible capabilities are made more robust).
Better now than later! Thanks, pulled.
Paolo