diff options
author | Paolo Bonzini <pbonzini@redhat.com> | 2017-02-08 11:50:15 +0100 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2017-02-17 12:27:37 +0100 |
commit | 460df4c1fc7c00829050c08d6368dc6e6beef307 (patch) | |
tree | 72c996f591c82ce12e2bc544ae9c9cc6e2aed81e /arch/arm/mach-ks8695 | |
parent | KVM: Support vCPU-based gfn->hva cache (diff) | |
download | linux-460df4c1fc7c00829050c08d6368dc6e6beef307.tar.xz linux-460df4c1fc7c00829050c08d6368dc6e6beef307.zip |
KVM: race-free exit from KVM_RUN without POSIX signals
The purpose of the KVM_SET_SIGNAL_MASK API is to let userspace "kick"
a VCPU out of KVM_RUN through a POSIX signal. A signal is attached
to a dummy signal handler; by blocking the signal outside KVM_RUN and
unblocking it inside, this possible race is closed:
VCPU thread service thread
--------------------------------------------------------------
check flag
set flag
raise signal
(signal handler does nothing)
KVM_RUN
However, one issue with KVM_SET_SIGNAL_MASK is that it has to take
tsk->sighand->siglock on every KVM_RUN. This lock is often on a
remote NUMA node, because it is on the node of a thread's creator.
Taking this lock can be very expensive if there are many userspace
exits (as is the case for SMP Windows VMs without Hyper-V reference
time counter).
As an alternative, we can put the flag directly in kvm_run so that
KVM can see it:
VCPU thread service thread
--------------------------------------------------------------
raise signal
signal handler
set run->immediate_exit
KVM_RUN
check run->immediate_exit
Reviewed-by: Radim Krčmář <rkrcmar@redhat.com>
Reviewed-by: David Hildenbrand <david@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'arch/arm/mach-ks8695')
0 files changed, 0 insertions, 0 deletions