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


Re: [Xen-devel] [PATCH 2/4] [HVM] introduce CPU affinity for allocate_ph

To: Christoph Egger <Christoph.Egger@xxxxxxx>
Subject: Re: [Xen-devel] [PATCH 2/4] [HVM] introduce CPU affinity for allocate_physmap call
From: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>
Date: Mon, 13 Aug 2007 23:00:44 +0900
Cc: Andre Przywara <andre.przywara@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Keir Fraser <keir@xxxxxxxxxxxxx>
Delivery-date: Mon, 13 Aug 2007 07:01:07 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200708131459.31305.Christoph.Egger@xxxxxxx>
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: <C2E5F147.14154%keir@xxxxxxxxxxxxx> <200708131459.31305.Christoph.Egger@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/
On Mon, Aug 13, 2007 at 02:59:31PM +0200, Christoph Egger wrote:
> > In this case we  could steal bits from address_bits field and create a pair
> > of 16-bit fields from it. Also, a physical cpu id is not a great fit for
> > this hypercall --  it is meaningless to most guests who do not see the
> > physical cpu map. 
> > Better to pass a vcpu_id and let Xen work out the most appropriate physical
> > cpu id based on the vcpu's affinity. Or have a concept of per-guest
> > 'virtual node identifiers' and pass a 'uint16_t vnodeid'. The latter might
> > actually be a nice abstraction -- it'd be good to know other people's
> > thoughts on this?
> Making struct xen_machphys_mapping NUMA-aware is also a no-go, right?
> It would additionally need a min_mfn and a vnodeid member.
> Oh, and how should the guest query how many vnode's exist?

Domain save/restore/dump-core also want to know those infomations.
Probably One approach is to introduce hypercalls or to store those
in xenstore. Another approach would be to introduce magic pages like
start_info, and embed it as reserved pages.

Xen-devel mailing list