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] [PATCH] docs: add a document about guest cpuid configuration

To: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [PATCH] docs: add a document about guest cpuid configuration
From: "Cui, Dexuan" <dexuan.cui@xxxxxxxxx>
Date: Mon, 14 Dec 2009 11:59:41 +0800
Accept-language: zh-CN, en-US
Acceptlanguage: zh-CN, en-US
Delivery-date: Sun, 13 Dec 2009 20:00:42 -0800
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: AcpzLo+VKU+4/M2URhqxF9ukgAQpBQJQpGrQ
Thread-topic: [PATCH] docs: add a document about guest cpuid configuration
CPUID emulation for guest

When HVM guest tries to execute CPUID, or PV guest tries to execute XEN_CPUID,
the xen hypervior traps and emultes them.

For HVM guest and PV DomU guest, xen's CPUID emulation can be adjusted using
the guest configation file if necessary (e.g., to supply better support for
guest live migration). The CPUID syntax in guest configration file is
described in detail in the examples like /etc/xen/xmexample.hvm,

However, a user (or an administrator) must be aware that the CPUID in guest
configuration file can NOT be configured casually. The default CPUID
configuration should be safe, but illegal configuration can cause unexpected
behaviors of guest -- even can crash guest.

For example, we should not expose the MONITOR CPUID feature flag (ECX bit 3;
CPUID executed EAX = 1) to HVM guest, otherwise, on guest's attempt of
executing MWAIT, the VMExit handler in Xen would inject #UD (Invalid Opcode
Exception) into the HVM guest, and guest kernel would panic.

/* We can add more unsafe CPUID configuration here in future. */
-- Dexuan

Attachment: doc_cpuid.patch
Description: doc_cpuid.patch

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [PATCH] docs: add a document about guest cpuid configuration, Cui, Dexuan <=