Re: [Xen-devel] PV-vNUMA issue: topology is misinterpreted by the guest

[Andrew Cooper <andrew.cooper3@xxxxxxxxxx>]

On 27/07/15 17:31, David Vrabel wrote:
>
>>> 2. For HVM guests, use the existing hardware interfaces to present NUMA
>>> topology.  i.e., CPUID, ACPI tables etc.  This will work for both kernel
>>> and userspace and both will see the same topology.
>>>
>>> This also has the advantage that any hypervisor/toolstack work will also
>>> be applicable to other guests (e.g., Windows).
>>>
>> Yeah, indeed. That's the downside of Juergen's "Linux scheduler
>> approach". But the issue is there, even without taking vNUMA into
>> account, and I think something like that would really help (only for
>> Dom0, and Linux guests, of course).
> I disagree.  Whether we're using vNUMA or not, Xen should still ensure
> that the guest kernel and userspace see a consistent and correct
> topology using the native mechanisms.

+1

~Andrew

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