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 1/4] hvm: NUMA guest: extend memops hypercall

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 1/4] hvm: NUMA guest: extend memops hypercall
From: Andre Przywara <andre.przywara@xxxxxxx>
Date: Fri, 4 Jul 2008 14:48:39 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 04 Jul 2008 05:49:25 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C493CF2F.238AC%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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <C493CF2F.238AC%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.10 (X11/20070409)
Keir Fraser wrote:
On 4/7/08 12:14, "Andre Przywara" <andre.przywara@xxxxxxx> wrote:

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.
Good catch (I code in HVM land most of the time), I hope this small
(attached) patch fixes this.

Looking some more, I still don't see that this patch can work. Don't the
subfunctions in memory.c go and OR in MEMF_node() values on top of what the
caller may have specified??
Maybe I don't get your question right, but the only part where the caller specified node number is used is the line I handled in the last patch. Later they only use the member memflags of struct memop_args, not struct xen_memory_reservation. If the node number is not specified (or blocked), it will be later determined by looking at the current scheduled pCPU (and thus node), but this is the current behavior anyway.

Regards,
Andre.

--
Andre Przywara
AMD-OSRC (Dresden)
Tel: x84917


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