On 07/24/2015 12:39 PM, Juergen Gross wrote:
I don't say mangling cpuids can't solve the scheduling problem. It
surely can. But it can't solve the scheduling problem without hiding
information like number of sockets or cores which might be required
for license purposes. If we don't care, fine.
(this is somewhat repeating the email I just sent)
Why can's we construct socket/core info with CPUID (and *possibly* ACPI
changes) that we present a reasonable (licensing-wise) picture?
Can you suggest an example where it will not work and then maybe we can
figure something out?
-boris
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
