diff options
author | Christoffer Dall <christoffer.dall@linaro.org> | 2017-10-04 23:42:32 +0200 |
---|---|---|
committer | Marc Zyngier <marc.zyngier@arm.com> | 2018-03-19 10:53:21 +0000 |
commit | 771621b0e2f80629948e0dc627d18b6730778c52 (patch) | |
tree | 8b023fc1bfa76949811657c65173baa66dfd789f /virt/kvm/arm/vgic/vgic-v3.c | |
parent | 8a43a2b34b7dc59dc6df5fa0a3b8540918bc4c58 (diff) | |
download | linux-stable-771621b0e2f80629948e0dc627d18b6730778c52.tar.gz linux-stable-771621b0e2f80629948e0dc627d18b6730778c52.tar.bz2 linux-stable-771621b0e2f80629948e0dc627d18b6730778c52.zip |
KVM: arm/arm64: Handle VGICv3 save/restore from the main VGIC code on VHE
Just like we can program the GICv2 hypervisor control interface directly
from the core vgic code, we can do the same for the GICv3 hypervisor
control interface on VHE systems.
We do this by simply calling the save/restore functions when we have VHE
and we can then get rid of the save/restore function calls from the VHE
world switch function.
One caveat is that we now write GICv3 system register state before the
potential early exit path in the run loop, and because we sync back
state in the early exit path, we have to ensure that we read a
consistent GIC state from the sync path, even though we have never
actually run the guest with the newly written GIC state. We solve this
by inserting an ISB in the early exit path.
Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'virt/kvm/arm/vgic/vgic-v3.c')
0 files changed, 0 insertions, 0 deletions