WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] porting xen-detect ASM code into a shared library

To: Guillaume Rousse <Guillaume.Rousse@xxxxxxxx>
Subject: Re: [Xen-devel] porting xen-detect ASM code into a shared library
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Thu, 10 Jul 2008 11:57:57 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 10 Jul 2008 03:58:41 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4875EA69.5040109@xxxxxxxx>
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: Acjie899DjuQZk5vEd2MOAAX8io7RQ==
Thread-topic: [Xen-devel] porting xen-detect ASM code into a shared library
User-agent: Microsoft-Entourage/11.4.0.080122
On 10/7/08 11:54, "Guillaume Rousse" <Guillaume.Rousse@xxxxxxxx> wrote:

> I turned it into the current way because I don't need the check in pv
> context, but I guess it might be simplified.

Actually then you can take the xc_cpuid_x86 function pretty much unmodified
(of course regs[0-3] become eax-edx, and input[1] is not needed).

The other stuff in the asm code is to ensure that cpuid traps into the
hypervisor when run in a pv guest. If you don't need to run in a pv guest
then you don't need that extra code.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel