mirror of https://gitee.com/openkylin/linux.git
94d0e5980d
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> |
||
|---|---|---|
| .. | ||
| Makefile | ||
| debug-sr.c | ||
| entry.S | ||
| fpsimd.S | ||
| hyp-entry.S | ||
| s2-setup.c | ||
| switch.c | ||
| sysreg-sr.c | ||
| tlb.c | ||