>From: Avi Kivity [mailto:[EMAIL PROTECTED] > >Indeed finer control over cpuid is needed. We need >to support at least three modes: > >- default: expose some machine that is likely to be widely supported >- host: expose as much of the host cpu as we can >- managed: management application controls everything >
[Nitin>] Avi, Would you like to elaborate more on these three mode's usage scenario? As I see, there are 2 things to look for while providing the cpuid to the guest. 1. Guest migration across different hosts. This limits exposed cpu features. 2. Utilizing host CPU features. This expands exposed cpu features. Both these needs should be accommodated keeping the flexibility to override. Thanks & Regards, Nitin Linux Open Source Technology Center, Intel Corporation ----------------------------------------------------------------------------- The Mind is like a parachute; it works much better when it's open. -- 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
