This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] cpuid information to hvm guest

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: [Xen-devel] cpuid information to hvm guest
From: "Kamble, Nitin A" <nitin.a.kamble@xxxxxxxxx>
Date: Mon, 29 Sep 2008 10:21:16 -0700
Accept-language: en-US
Acceptlanguage: en-US
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Mon, 29 Sep 2008 10:21:56 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AckiV8fr9iS1sXiMSTKzJGUXP4rdAA==
Thread-topic: cpuid information to hvm guest



Currently guest is seeing broken thread/core siblings topology because some of cupid bits are getting blocked by default.


With the attached 2 patches hvm guest will see same topology as the host-os sees.


It is still possible to override these bits in the guest config file, so that migration across different topology system can work.


Please apply.



Thanks & Regards,


Linux Open Source Technology Center, Intel Corporation


The Mind is like a parachute; it works much better when it's open.


Attachment: xc_cpuid_1.patch
Description: xc_cpuid_1.patch

Attachment: lapicid_1.patch
Description: lapicid_1.patch

Xen-devel mailing list