On 12/12/19 18:43, Sean Christopherson wrote: > Key word being "usually". My intent in printing out partially redundant > flags was to help users debug/understand why the combined feature isn't > supported. E.g. userspace can already easily (relatively speaking) query > flexpriority support via /sys/module/kvm_intel/parameters/flexpriority. > But if that comes back "N", the user has no way to determine exactly why > flexpriority is disabled. There are tools such as vmxcap. It is part of QEMU, but I wouldn't mind moving it into the kernel tree. Paolo
