Hi, Gentle ping on this patch (CPUID leaf 4 trap for WHPX). It is still on patchew awaiting review; is there anything I can do to move it forward (rebase, commit message, or splitting the six-fix series)?
While debugging further on the same Windows/AMD host I isolated two more WHPX defects that look worth sending as follow-up patches, both of which reproduce guest-visible corruption: 1. Stale XSAVE image written back into Hyper-V. On this host WHvGetVirtualProcessorState(Xsave) fails on every call, so QEMU's env FP/SSE/AVX image is never refreshed; any vm_stop/vm_start cycle (gdb attach, QMP stop, migration pause) then writes the stale image back and clobbers live vector registers on all VPs, corrupting the guest. Proposed fix: track xsave validity per VP and skip the write-back when the read never succeeded. 2. MemoryAccess MMIO dispatch runs without the BQL. whpx_vcpu_run drops the BQL before WHvRunVirtualProcessor and the MemoryAccess exit path never reacquires it, so device MMIO handlers run BQL-free on vCPU threads (KVM/TCG/HVF all dispatch MMIO under the BQL). Devices touching MemoryRegion state race the main loop. Proposed fix: take the BQL around emulate_instruction in whpx_handle_mmio. I can post both as proper patches if they are not already known / in flight. Happy to follow the project's AI-contribution policy statement as discussed. Thanks, Jiajun Liang
