Alexander Graf wrote:
I don't believe we need a userspace interface for now. The userspace part does not need to know what capabilities the virtual CPU has - that's what the CPUID masking in the kvm code is for IMHO.
It's the other way round. The kernel exposes which features are available, and userspace decides what to present to the guest. Kernel masking means userspace doesn't really know what the guest sees.
The existing masking in the kernel is due to bugs. -- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
