Paul Brook wrote:
What you really want to do is ask your virtualization module what features it supports.Yes, that needs to be an additional filter.I'd have thought that would be the *only* interesting set for autodetection.
Yes, you're right. It's pointless to issue cpuid in userspace and mask it in the kernel; rather we can issue it in the kernel , mask out unsupported features, and return it to userspace.
-- error compiling committee.c: too many arguments to function
