diff options
| author | Fuad Tabba <tabba@google.com> | 2021-10-10 15:56:36 +0100 |
|---|---|---|
| committer | Marc Zyngier <maz@kernel.org> | 2021-10-11 14:57:30 +0100 |
| commit | 5f39efc42052b042c4d7ba6fd77934e8de43e10c (patch) | |
| tree | 0c5457c13c68cbc0fa3332bf1103973716b6ad43 /tools/perf/scripts/python/mem-phys-addr.py | |
| parent | 1423afcb411780c7a6a68f801fdcfb6920ad6f06 (diff) | |
KVM: arm64: Handle protected guests at 32 bits
Protected KVM does not support protected AArch32 guests. However,
it is possible for the guest to force run AArch32, potentially
causing problems. Add an extra check so that if the hypervisor
catches the guest doing that, it can prevent the guest from
running again by resetting vcpu->arch.target and returning
ARM_EXCEPTION_IL.
If this were to happen, The VMM can try and fix it by re-
initializing the vcpu with KVM_ARM_VCPU_INIT, however, this is
likely not possible for protected VMs.
Adapted from commit 22f553842b14 ("KVM: arm64: Handle Asymmetric
AArch32 systems")
Signed-off-by: Fuad Tabba <tabba@google.com>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Link: https://lore.kernel.org/r/20211010145636.1950948-12-tabba@google.com
Diffstat (limited to 'tools/perf/scripts/python/mem-phys-addr.py')
0 files changed, 0 insertions, 0 deletions