If a VMM wants to leverage the VMXOFF behavior, software enumerationYeah, F/M/S is a bad idea. Architecturally, I think the behavior needs to be
might be needed for nested virtualization. Using CPU F/M/S (SPR+) to
enumerate a behavior could be problematic for virtualization. Right?
tied to support for SEAM. Is there a safe-ish way to probe for SEAM support,
without having to glean it from MSR_IA32_MKTME_KEYID_PARTITIONING?