bf9bf2306c
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> |
||
---|---|---|
.. | ||
hvf-cpu.c | ||
hvf-i386.h | ||
hvf.c | ||
meson.build | ||
panic.h | ||
README.md | ||
vmcs.h | ||
vmx.h | ||
x86_cpuid.c | ||
x86_decode.c | ||
x86_decode.h | ||
x86_descr.c | ||
x86_descr.h | ||
x86_emu.c | ||
x86_emu.h | ||
x86_flags.c | ||
x86_flags.h | ||
x86_mmu.c | ||
x86_mmu.h | ||
x86_task.c | ||
x86_task.h | ||
x86.c | ||
x86.h | ||
x86hvf.c | ||
x86hvf.h |
OS X Hypervisor.framework support in QEMU
These sources (and ../hvf-all.c) are adapted from Veertu Inc's vdhh (Veertu Desktop Hosted Hypervisor) (last known location: https://github.com/veertuinc/vdhh) with some minor changes, the most significant of which were:
- Adapt to our current QEMU's
CPUState
structure andaddress_space_rw
API; many struct members have been moved around (emulated x86 state, xsave_buf) due to historical differences + QEMU needing to handle more emulation targets. - Removal of
apic_page
and hyperv-related functionality. - More relaxed use of
bql_lock
.