On Fri, Nov 14, 2025 at 10:35:41AM -0800, Sean Christopherson wrote: > On Fri, Nov 14, 2025, Wei Liu wrote: > > On Fri, Nov 14, 2025 at 07:22:41AM -0800, Sean Christopherson wrote: > > > Ah, my PDF copy is just stale, it's indeed > > > defined as a synthetic exit. > > > > > > > > > https://learn.microsoft.com/en-us/virtualization/hyper-v-on-windows/tlfs/nested-virtualization#synthetic-vm-exit > > > > > > Anyways, I'm in favor of making HV_SVM_EXITCODE_ENL an ull, though part > > > of me > > > wonders if we should do: > > > > > > #define HV_SVM_EXITCODE_ENL SVM_EXIT_SW > > > > I know this is very tempting, but these headers are supposed to mirror > > Microsoft's internal headers, so we would like to keep them > > self-contained for ease of tracking. > > Ya, no argument from me. Aha! Even better, what I can do is have KVM assert > that HV_SVM_EXITCODE_ENL == SVM_EXIT_SW in the KVM Hyper-V code, because what > I > really want to do is connect the dots for KVM folks.
This sounds like a good plan. Wei
