summaryrefslogtreecommitdiff
path: root/drivers/crypto/Kconfig
diff options
context:
space:
mode:
authorMarc Zyngier <marc.zyngier@arm.com>2019-07-06 01:35:56 +0300
committerMarc Zyngier <marc.zyngier@arm.com>2019-07-08 18:29:48 +0300
commit1e0cf16cdad1ba53e9eeee8746fe57de42f20c97 (patch)
tree664d34bdb34d0e9e7ee193932c225ed49a4db80e /drivers/crypto/Kconfig
parentfdec2a9ef853172529baaa192673b4cdb9a44fac (diff)
downloadlinux-1e0cf16cdad1ba53e9eeee8746fe57de42f20c97.tar.xz
KVM: arm/arm64: Initialise host's MPIDRs by reading the actual register
As part of setting up the host context, we populate its MPIDR by using cpu_logical_map(). It turns out that contrary to arm64, cpu_logical_map() on 32bit ARM doesn't return the *full* MPIDR, but a truncated version. This leaves the host MPIDR slightly corrupted after the first run of a VM, since we won't correctly restore the MPIDR on exit. Oops. Since we cannot trust cpu_logical_map(), let's adopt a different strategy. We move the initialization of the host CPU context as part of the per-CPU initialization (which, in retrospect, makes a lot of sense), and directly read the MPIDR from the HW. This is guaranteed to work on both arm and arm64. Reported-by: Andre Przywara <Andre.Przywara@arm.com> Tested-by: Andre Przywara <Andre.Przywara@arm.com> Fixes: 32f139551954 ("arm/arm64: KVM: Statically configure the host's view of MPIDR") Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'drivers/crypto/Kconfig')
0 files changed, 0 insertions, 0 deletions