diff options
author | Phil Dennis-Jordan <phil@philjordan.eu> | 2024-06-05 13:25:54 +0200 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2024-06-08 10:33:38 +0200 |
commit | bf9bf2306cc8ea31b2b9bf28002aacb188ec2568 (patch) | |
tree | 0c49f61880451918a92e63f7b3ba4569a8094953 /qemu-keymap.c | |
parent | 3e2c6727cb6b6311ee129c24b561bb87495f1a25 (diff) | |
download | qemu-bf9bf2306cc8ea31b2b9bf28002aacb188ec2568.zip qemu-bf9bf2306cc8ea31b2b9bf28002aacb188ec2568.tar.gz qemu-bf9bf2306cc8ea31b2b9bf28002aacb188ec2568.tar.bz2 |
i386/hvf: In kick_vcpu use hv_vcpu_interrupt to force exit
When interrupting a vCPU thread, this patch actually tells the hypervisor to
stop running guest code on that vCPU.
Calling hv_vcpu_interrupt actually forces a vCPU exit, analogously to
hv_vcpus_exit on aarch64. Alternatively, if the vCPU thread
is not
running the VM, it will immediately cause an exit when it attempts
to do so.
Previously, hvf_kick_vcpu_thread relied upon hv_vcpu_run returning very
frequently, including many spurious exits, which made it less of a problem that
nothing was actively done to stop the vCPU thread running guest code.
The newer, more efficient hv_vcpu_run_until exits much more rarely, so a true
"kick" is needed before switching to that.
Signed-off-by: Phil Dennis-Jordan <phil@philjordan.eu>
Message-ID: <20240605112556.43193-6-phil@philjordan.eu>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'qemu-keymap.c')
0 files changed, 0 insertions, 0 deletions