Searched hist:"2 a0c343386ae1a6826e1b9d751bfc14f4711c2de" (Results 1 – 2 of 2) sorted by relevance
/linux/arch/arm64/kvm/hyp/nvhe/ |
H A D | pkvm.c | 2a0c343386ae1a6826e1b9d751bfc14f4711c2de Sun Oct 10 16:56:33 CEST 2021 Fuad Tabba <tabba@google.com> KVM: arm64: Initialize trap registers for protected VMs
Protected VMs have more restricted features that need to be trapped. Moreover, the host should not be trusted to set the appropriate trapping registers and their values.
Initialize the trapping registers, i.e., hcr_el2, mdcr_el2, and cptr_el2 at EL2 for protected guests, based on the values of the guest's feature id registers.
No functional change intended as trap handlers introduced in the previous patch are still not hooked in to the guest exit handlers.
Reviewed-by: Andrew Jones <drjones@redhat.com> Signed-off-by: Fuad Tabba <tabba@google.com> Signed-off-by: Marc Zyngier <maz@kernel.org> Link: https://lore.kernel.org/r/20211010145636.1950948-9-tabba@google.com
|
H A D | Makefile | diff 2a0c343386ae1a6826e1b9d751bfc14f4711c2de Sun Oct 10 16:56:33 CEST 2021 Fuad Tabba <tabba@google.com> KVM: arm64: Initialize trap registers for protected VMs
Protected VMs have more restricted features that need to be trapped. Moreover, the host should not be trusted to set the appropriate trapping registers and their values.
Initialize the trapping registers, i.e., hcr_el2, mdcr_el2, and cptr_el2 at EL2 for protected guests, based on the values of the guest's feature id registers.
No functional change intended as trap handlers introduced in the previous patch are still not hooked in to the guest exit handlers.
Reviewed-by: Andrew Jones <drjones@redhat.com> Signed-off-by: Fuad Tabba <tabba@google.com> Signed-off-by: Marc Zyngier <maz@kernel.org> Link: https://lore.kernel.org/r/20211010145636.1950948-9-tabba@google.com
|