Re: [PATCH RFC 0/8] x86/hvm, libxl: HVM SMT topology support

[Andrew Cooper <andrew.cooper3@citrix.com>]

On 26/02/16 15:42, Dario Faggioli wrote:
> On Fri, 2016-02-26 at 10:27 -0500, Konrad Rzeszutek Wilk wrote:
>> On Fri, Feb 26, 2016 at 04:03:46PM +0100, Dario Faggioli wrote:
>>>  
>>>> As part of my further cpuid work, I will need to fix this.  I was
>>>> planning to fix it by requiring full cpu topology information to
>>>> be
>>>> passed as part of the domaincreate or max_vcpus hypercall  (not
>>>> chosen
>>>> which yet).  
>> You may not want to make a full CPU topology to be exposed to the
>> guest.
>>
> Right, but if I understood correctly (and, actually, to confirm that is
> what I'm asking), what's Andrew is saying does not mean "always expose
> the host topology". It means that a guest must have a (virtual)
> topology, and that topology can be Xen's default one, toolstack's
> default one, toolstack's default one when vcpu pinning is on, one that
> the administrator like, etc.

Correct.  As far as this goes, I don't care whether the topology the
guest sees matches the host topology or not.  What I care about is the
guest seeing a plausible topology, conforming to the rules set out by
the Intel/AMD manuals.

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel