[PATCH 3/3] KVM: arm64: Handle SCXTNUM_ELx traps

As the kernel never sets HCR_EL2.EnSCXT, accesses to SCXTNUM_ELx will trap to EL2. Let's handle that as gracefully as possible by injecting an UNDEF exception into the guest. This is consistent with the guest's view of ID_AA64PFR0_EL1.CSV2 being at most 1. Signed-off-by: Marc Zyngier Acked-by:

Re: [PATCH 3/3] KVM: arm64: Handle SCXTNUM_ELx traps

On Tue, Nov 03, 2020 at 05:14:45PM +, Marc Zyngier wrote: > As the kernel never sets HCR_EL2.EnSCXT, accesses to SCXTNUM_ELx > will trap to EL2. Let's handle that as gracefully as possible > by injecting an UNDEF exception into the guest. This is consistent > with the guest's view of

[PATCH 3/3] KVM: arm64: Handle SCXTNUM_ELx traps

As the kernel never sets HCR_EL2.EnSCXT, accesses to SCXTNUM_ELx will trap to EL2. Let's handle that as gracefully as possible by injecting an UNDEF exception into the guest. This is consistent with the guest's view of ID_AA64PFR0_EL1.CSV2 being at most 1. Signed-off-by: Marc Zyngier ---