Re: [Xen-devel] [PATCH 02/19] xen: make two memory hypercalls vNUMA-aware

2014-11-21 Thread Wei Liu
On Fri, Nov 21, 2014 at 05:03:09PM +, Jan Beulich wrote: > >>> On 21.11.14 at 16:06, wrote: > > @@ -747,6 +786,17 @@ long do_memory_op(unsigned long cmd, > > XEN_GUEST_HANDLE_PARAM(void) arg) > > return start_extent; > > args.domain = d; > > > > +args.memflags

Re: [Xen-devel] [PATCH 02/19] xen: make two memory hypercalls vNUMA-aware

2014-11-21 Thread Jan Beulich
>>> On 21.11.14 at 16:06, wrote: > @@ -747,6 +786,17 @@ long do_memory_op(unsigned long cmd, > XEN_GUEST_HANDLE_PARAM(void) arg) > return start_extent; > args.domain = d; > > +args.memflags |= MEMF_node(XENMEMF_get_node(reservation.mem_flags)); > +if ( rese

[Xen-devel] [PATCH 02/19] xen: make two memory hypercalls vNUMA-aware

2014-11-21 Thread Wei Liu
Make XENMEM_increase_reservation and XENMEM_populate_physmap vNUMA-aware. That is, if guest requests Xen to allocate memory for specific vnode, Xen can translate vnode to pnode using vNUMA information of that guest. XENMEMF_vnode is introduced for the guest to mark the node number is in fact virt