Marc Zyngier 94d0e5980d arm/arm64: KVM: Perform local TLB invalidation when multiplexing vcpus on a single CPU ... Architecturally, TLBs are private to the (physical) CPU they're associated with. But when multiple vcpus from the same VM are being multiplexed on the same CPU, the TLBs are not private to the vcpus (and are actually shared across the VMID). Let's consider the following scenario: - vcpu-0 maps PA to VA - vcpu-1 maps PA' to VA If run on the same physical CPU, vcpu-1 can hit TLB entries generated by vcpu-0 accesses, and access the wrong physical page. The solution to this is to keep a per-VM map of which vcpu ran last on each given physical CPU, and invalidate local TLBs when switching to a different vcpu from the same VM. Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>		2016-11-04 17:56:28 +00:00
..
banked-sr.c	ARM: KVM: Move kvm/hyp/hyp.h to include/asm/kvm_hyp.h	2016-02-29 18:34:18 +00:00
cp15-sr.c	ARM: KVM: Move kvm/hyp/hyp.h to include/asm/kvm_hyp.h	2016-02-29 18:34:18 +00:00
entry.S	arm: KVM: Handle async aborts delivered while at HYP	2016-09-08 12:53:00 +02:00
hyp-entry.S	arm: KVM: Handle async aborts delivered while at HYP	2016-09-08 12:53:00 +02:00
Makefile	ARM: KVM: Support vgic-v3	2016-09-22 13:22:21 +02:00
s2-setup.c	ARM: KVM: Move kvm/hyp/hyp.h to include/asm/kvm_hyp.h	2016-02-29 18:34:18 +00:00
switch.c	ARM: KVM: Support vgic-v3	2016-09-22 13:22:21 +02:00
tlb.c	arm/arm64: KVM: Perform local TLB invalidation when multiplexing vcpus on a single CPU	2016-11-04 17:56:28 +00:00
vfp.S	ARM: KVM: Add VFP save/restore	2016-02-29 18:34:13 +00:00