diff options
author | Marc Zyngier <marc.zyngier@arm.com> | 2018-07-10 13:20:47 +0100 |
---|---|---|
committer | Marc Zyngier <marc.zyngier@arm.com> | 2018-07-21 16:02:17 +0100 |
commit | 9bc03f1df31a3228289d5046780071ab8e91aa1a (patch) | |
tree | e5f245c1a5842ffee1e285aa618b04bc55a0939b /virt | |
parent | e294cb3a6d1a8967a83b5f083d4f463e2dc28b61 (diff) | |
download | linux-stable-9bc03f1df31a3228289d5046780071ab8e91aa1a.tar.gz linux-stable-9bc03f1df31a3228289d5046780071ab8e91aa1a.tar.bz2 linux-stable-9bc03f1df31a3228289d5046780071ab8e91aa1a.zip |
arm64: KVM: Cleanup tpidr_el2 init on non-VHE
When running on a non-VHE system, we initialize tpidr_el2 to
contain the per-CPU offset required to reach per-cpu variables.
Actually, we initialize it twice: the first time as part of the
EL2 initialization, by copying tpidr_el1 into its el2 counterpart,
and another time by calling into __kvm_set_tpidr_el2.
It turns out that the first part is wrong, as it includes the
distance between the kernel mapping and the linear mapping, while
EL2 only cares about the linear mapping. This was the last vestige
of the first per-cpu use of tpidr_el2 that came in with SDEI.
The only caller then was hyp_panic(), and its now using the
pc-relative get_host_ctxt() stuff, instead of kimage addresses
from the literal pool.
It is not a big deal, as we override it straight away, but it is
slightly confusing. In order to clear said confusion, let's
set this directly as part of the hyp-init code, and drop the
ad-hoc HYP helper.
Reviewed-by: James Morse <james.morse@arm.com>
Acked-by: Christoffer Dall <christoffer.dall@arm.com>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions