aboutsummaryrefslogtreecommitdiffstats
path: root/include/kvm
diff options
context:
space:
mode:
authorMarc Zyngier <maz@kernel.org>2020-11-26 17:27:13 +0000
committerMarc Zyngier <maz@kernel.org>2020-11-30 16:02:53 +0000
commit4f1df628d4ec22b04f67e068e6d02538d3dd557b (patch)
treeda117b4f2caab5247116ef5cb944781e1291ba65 /include/kvm
parent7f43c2014fa03bb8718569ae628acf2089683bff (diff)
downloadlinux-4f1df628d4ec22b04f67e068e6d02538d3dd557b.tar.gz
KVM: arm64: Advertise ID_AA64PFR0_EL1.CSV3=1 if the CPUs are Meltdown-safe
Cores that predate the introduction of ID_AA64PFR0_EL1.CSV3 to the ARMv8 architecture have this field set to 0, even of some of them are not affected by the vulnerability. The kernel maintains a list of unaffected cores (A53, A55 and a few others) so that it doesn't impose an expensive mitigation uncessarily. As we do for CSV2, let's expose the CSV3 property to guests that run on HW that is effectively not vulnerable. This can be reset to zero by writing to the ID register from userspace, ensuring that VMs can be migrated despite the new property being set. Reported-by: Will Deacon <will@kernel.org> Signed-off-by: Marc Zyngier <maz@kernel.org>
Diffstat (limited to 'include/kvm')
0 files changed, 0 insertions, 0 deletions