diff options
author | Christoffer Dall <christoffer.dall@linaro.org> | 2018-02-27 12:33:50 +0100 |
---|---|---|
committer | Marc Zyngier <marc.zyngier@arm.com> | 2018-03-14 19:29:14 +0100 |
commit | e21a4f3a930cda6e4902cb5b3213365e5ff3ce7c (patch) | |
tree | 6200880064b9c113f5498186ac1ac704427d61ca /include/kvm | |
parent | KVM: arm/arm64: vgic: Add missing irq_lock to vgic_mmio_read_pending (diff) | |
download | linux-e21a4f3a930cda6e4902cb5b3213365e5ff3ce7c.tar.xz linux-e21a4f3a930cda6e4902cb5b3213365e5ff3ce7c.zip |
KVM: arm/arm64: Avoid vcpu_load for other vcpu ioctls than KVM_RUN
Calling vcpu_load() registers preempt notifiers for this vcpu and calls
kvm_arch_vcpu_load(). The latter will soon be doing a lot of heavy
lifting on arm/arm64 and will try to do things such as enabling the
virtual timer and setting us up to handle interrupts from the timer
hardware.
Loading state onto hardware registers and enabling hardware to signal
interrupts can be problematic when we're not actually about to run the
VCPU, because it makes it difficult to establish the right context when
handling interrupts from the timer, and it makes the register access
code difficult to reason about.
Luckily, now when we call vcpu_load in each ioctl implementation, we can
simply remove the call from the non-KVM_RUN vcpu ioctls, and our
kvm_arch_vcpu_load() is only used for loading vcpu content to the
physical CPU when we're actually going to run the vcpu.
Cc: stable@vger.kernel.org
Fixes: 9b062471e52a ("KVM: Move vcpu_load to arch-specific kvm_arch_vcpu_ioctl")
Reviewed-by: Julien Grall <julien.grall@arm.com>
Reviewed-by: Marc Zyngier <marc.zyngier@arm.com>
Reviewed-by: Andrew Jones <drjones@redhat.com>
Signed-off-by: Christoffer Dall <christoffer.dall@linaro.org>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Diffstat (limited to 'include/kvm')
0 files changed, 0 insertions, 0 deletions