aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/virt
diff options
context:
space:
mode:
authorArd Biesheuvel <ard.biesheuvel@linaro.org>2019-01-31 14:17:17 +0100
committerMarc Zyngier <marc.zyngier@arm.com>2019-02-19 21:05:48 +0000
commitf7f2b15c3d42fa5754131b34a0f7ad5a5c3f777f (patch)
treef905ad3b4c33c87154c0c2afbac8a548b0827fec /virt
parentKVM: arm/arm64: Move kvm_is_write_fault to header file (diff)
downloadwireguard-linux-f7f2b15c3d42fa5754131b34a0f7ad5a5c3f777f.tar.xz
wireguard-linux-f7f2b15c3d42fa5754131b34a0f7ad5a5c3f777f.zip
arm64: KVM: Expose sanitised cache type register to guest
We currently permit CPUs in the same system to deviate in the exact topology of the caches, and we subsequently hide this fact from user space by exposing a sanitised value of the cache type register CTR_EL0. However, guests running under KVM see the bare value of CTR_EL0, which could potentially result in issues with, e.g., JITs or other pieces of code that are sensitive to misreported cache line sizes. So let's start trapping cache ID instructions if there is a mismatch, and expose the sanitised version of CTR_EL0 to guests. Note that CTR_EL0 is treated as an invariant to KVM user space, so update that part as well. Acked-by: Christoffer Dall <christoffer.dall@arm.com> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions