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] [PATCH][retry 2][2/2] new platform hypervisor call to ge

To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, "Jan Beulich" <jbeulich@xxxxxxxxxx>
Subject: RE: [Xen-devel] [PATCH][retry 2][2/2] new platform hypervisor call to get APICIDs
From: "Langsdorf, Mark" <mark.langsdorf@xxxxxxx>
Date: Tue, 4 Mar 2008 12:00:54 -0600
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Chris Lalancette <clalance@xxxxxxxxxx>
Delivery-date: Tue, 04 Mar 2008 10:03:57 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C3F2E663.1D703%keir.fraser@xxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C3F2C77B.1D64D%keir.fraser@xxxxxxxxxxxxx> <C3F2E663.1D703%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Ach92oxJyw4AQOnNEdyzcwAX8io7RQAEmvpYAA0kC+A=
Thread-topic: [Xen-devel] [PATCH][retry 2][2/2] new platform hypervisor call to get APICIDs
> > Anyway, if we make it a singleton-apicid vcpu_op, which 
> > fails on anything other than a pinned dom0

Will do.

> Also there is no particular reason not to have this vcpu_op return the
> acpiid as well. Call it something like VCPUOP_phys_id, returns an
> arch-specific uint64_t phys_id. On x86 we could have 8-bit 
> apicid plus 8-bit acpiid packed into that uint64_t, with the
> other 48 bits being MBZ for future expansion (e.g., x2apic extra
> id bits should we ever care). Either id can be 0xff indicating
> 'not available'.

Okay.  I'll add that.

-Mark Langsdorf
Operating System Research Center
AMD


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