Vitaly Kuznetsov <vkuznets@xxxxxxxxxx> writes: ... > > While on it, update the comment why VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL/ > VM_ENTRY_LOAD_IA32_PERF_GLOBAL_CTRL are kept filtered out ... > + * While GUEST_IA32_PERF_GLOBAL_CTRL and HOST_IA32_PERF_GLOBAL_CTRL > + * are present in eVMCSv1, Windows 11 still has issues booting when > + * VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL/VM_ENTRY_LOAD_IA32_PERF_GLOBAL_CTRL > + * are exposed to it, keep them filtered out. Finally, I got a piece of information from Microsoft on what's going on and it solves a lot of our problems. They did introduce a new PV feature bit indicating support for these new fields in eVMCSv1 and Win11 checks for its presence. This means that we do not need to play the 'eVMCS revisions' trick as CPUID information from VMM is enough. -- Vitaly
