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

Re: [Xen-devel] [PATCH 1/4] hvm: NUMA guest: extend memops hypercall


  • To: Andre Przywara <andre.przywara@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
  • Date: Fri, 04 Jul 2008 10:52:47 +0100
  • Cc:
  • Delivery-date: Fri, 04 Jul 2008 02:53:16 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Acjdu7Z49LwlcEmuEd2bbwAX8io7RQ==
  • Thread-topic: [Xen-devel] [PATCH 1/4] hvm: NUMA guest: extend memops hypercall

On 4/7/08 08:57, "Andre Przywara" <andre.przywara@xxxxxxx> wrote:

> This patch extends the memops hypercall in a compatible way to transport
> a desired NUMA node number. The address_bits field will be limited to 8
> bits and is now embedded in the mem_flags member, which additionally
> contains the node number (limited to 8 bit). Passing a node number of
> '0' (currently the default) will revert to automatic node selection
> (based on currently scheduled node).
> 
> Signed-off-by: Andre Przywara <andre.przywara@xxxxxxx>

Should unprivileged domUs be allowed to specify the NUMA node they allocate
from, regardless of whether they even run there? Seems like a breakage of
guest isolation to me.

 -- Keir



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


 


Rackspace

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