summaryrefslogtreecommitdiffstats
path: root/samples
diff options
context:
space:
mode:
authorMarc Zyngier <maz@kernel.org>2022-05-28 12:38:12 +0100
committerMarc Zyngier <maz@kernel.org>2022-06-07 14:31:30 +0100
commit039f49c4cafb785504c678f28664d088e0108d35 (patch)
tree8f2c06282485751d8da9b8a4c7fc924a023cc516 /samples
parentd52d165d67c5aa26c8c89909003c94a66492d23d (diff)
downloadlinux-039f49c4cafb785504c678f28664d088e0108d35.tar.bz2
KVM: arm64: Always start with clearing SME flag on load
On each vcpu load, we set the KVM_ARM64_HOST_SME_ENABLED flag if SME is enabled for EL0 on the host. This is used to restore the correct state on vpcu put. However, it appears that nothing ever clears this flag. Once set, it will stick until the vcpu is destroyed, which has the potential to spuriously enable SME for userspace. As it turns out, this is due to the SME code being more or less copied from SVE, and inheriting the same shortcomings. We never saw the issue because nothing uses SME, and the amount of testing is probably still pretty low. Fixes: 861262ab8627 ("KVM: arm64: Handle SME host state when running guests") Signed-off-by: Marc Zyngier <maz@kernel.org> Reviwed-by: Mark Brown <broonie@kernel.org> Link: https://lore.kernel.org/r/20220528113829.1043361-3-maz@kernel.org
Diffstat (limited to 'samples')
0 files changed, 0 insertions, 0 deletions