Re: thread/core siblings info for guests

[Chris Wright <chrisw@sous-sol.org>]

* Kamble, Nitin A (nitin.a.kamble@intel.com) wrote:
> >From: Avi Kivity [mailto:avi@redhat.com]
> >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
> 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.

This falls under managed above, as it's smth the mgmt app knows (e.g. what's the
least common denominator in your migration pool?).

>    2. Utilizing host CPU features. This expands exposed cpu features.

This falls under host above.

And the default mode above is just about picking a sane default.

thanks,
-chris