bcdc508190
It's going to clutter QEMU logs if 0x0f00 is trapped. Signed-off-by: Roman Bolshakov <r.bolshakov@yadro.com> Message-Id: <20181203100415.53027-2-r.bolshakov@yadro.com> Signed-off-by: Laurent Vivier <laurent@vivier.eu> |
||
---|---|---|
.. | ||
hvf-i386.h | ||
hvf.c | ||
Makefile.objs | ||
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
qemu_mutex_lock_iothread
.