> I think it would be better to say that the userspace should enable > MONITOR in CPUID when using KVM_X86_DISABLE_EXITS_MWAIT. The problem with that approach is that it breaks the documented API for KVM_GET_SUPPORTED_CPUID. Specifically, "This ioctl returns x86 cpuid features which are supported by both the hardware and kvm." If, for example, we use KVM_GET_SUPPORTED_CPUID to determine whether or not a target host can support a live migration, then it becomes impossible to migrate a guest that uses KVM_X86_DISABLE_EXITS_MWAIT. Perhaps, like Intel, we have painted ourselves into a corner, and now we need KVM_GET_TRUE_SUPPORTED_CPUID?
