[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

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



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.