Quentin Perret bfa79a8054 KVM: arm64: Elevate hypervisor mappings creation at EL2 ... Previous commits have introduced infrastructure to enable the EL2 code to manage its own stage 1 mappings. However, this was preliminary work, and none of it is currently in use. Put all of this together by elevating the mapping creation at EL2 when memory protection is enabled. In this case, the host kernel running at EL1 still creates _temporary_ EL2 mappings, only used while initializing the hypervisor, but frees them right after. As such, all calls to create_hyp_mappings() after kvm init has finished turn into hypercalls, as the host now has no 'legal' way to modify the hypevisor page tables directly. Acked-by: Will Deacon <will@kernel.org> Signed-off-by: Quentin Perret <qperret@google.com> Signed-off-by: Marc Zyngier <maz@kernel.org> Link: https://lore.kernel.org/r/20210319100146.1149909-19-qperret@google.com		2021-03-19 12:01:21 +00:00
..
asm	KVM: arm64: Elevate hypervisor mappings creation at EL2	2021-03-19 12:01:21 +00:00
uapi/asm	KVM: arm64: Move 'struct kvm_arch_memory_slot' out of uapi/	2020-11-27 18:59:05 +00:00