Xen project Mailing List

Re: [Xen-devel] fewer CPUID instructions is monitored/emulated in xen 4.0.1 than in xen 3.1.0?

To: "K.C. Lee" <kcl.joseph@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>

From: Keir Fraser <keir@xxxxxxx>

Date: Thu, 07 Oct 2010 13:40:50 +0100

Cc:

Delivery-date: Thu, 07 Oct 2010 05:41:42 -0700

Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:user-agent:date:subject:from:to:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=PVpMBdg7mSiz7D4PH4rESX+XBcKR3SXsG2oB2/K+2L/QyEEGBtj7GAU//H8Q2tH5br ToXK4m67XQqpebOXi++lDXqpNK0v6kaTFsL2D6n9kBpyznIkXZaY8EIkst0isnoi/fYk 3q67Zrzb2Q41vjDitJ8COCJcmd1o09mhpFJ+8=

List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Thread-index: ActmHN8zKNhve0Wsdk6Z9Xa2sLgXAQ==

Thread-topic: [Xen-devel] fewer CPUID instructions is monitored/emulated in xen 4.0.1 than in xen 3.1.0?

Guest CPUID information gets pushed into the hypervisor from the toolstack now. See tools/libxc/xc_cpuid_x86.c. -- Keir On 07/10/2010 10:42, "K.C. Lee" <kcl.joseph@xxxxxxxxx> wrote: > Hi, > > In the function vmx_do_cpuid() of xen 4.0.1, it calls vmx_cpuid_intercept() > which > deal with the case where eax is 0x80000001 only, > much less than the cases in vmx_do_cpuid() of xen 3.1.0. > > Does that mean fewer instructions is monitored in xen 4.0.1? Why? > > Thank you. > > Sincerely, > > K.C. > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@xxxxxxxxxxxxxxxxxxx > http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.