xemu/target/i386/hvf
mborgerson 52c6a60949 deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
..
README.md deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
hvf-cpu.c deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
hvf-i386.h deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
hvf.c deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
meson.build deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
panic.h deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
vmcs.h deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
vmx.h deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
x86.c deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
x86.h deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
x86_cpuid.c deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
x86_decode.c deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
x86_decode.h deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
x86_descr.c deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
x86_descr.h deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
x86_emu.c deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
x86_emu.h deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
x86_flags.c deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
x86_flags.h deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
x86_mmu.c deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
x86_mmu.h deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
x86_task.c deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
x86_task.h deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
x86hvf.c deploy: 0c2a617819 2025-04-18 19:07:03 +00:00
x86hvf.h deploy: 0c2a617819 2025-04-18 19:07:03 +00:00

README.md

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:

  1. Adapt to our current QEMU's CPUState structure and address_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.
  2. Removal of apic_page and hyperv-related functionality.
  3. More relaxed use of bql_lock.