From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH v4 17/21] libxl: disallow memory relocation
 when vNUMA is enabled
Date: Thu, 29 Jan 2015 11:06:07 +0000
Message-ID: <1422529567.30641.38.camel@citrix.com>
References: <1422011632-22018-1-git-send-email-wei.liu2@citrix.com>
	<1422011632-22018-18-git-send-email-wei.liu2@citrix.com>
	<1422463271.5187.63.camel@citrix.com>
	<20150128222225.GF14935@zion.uk.xensource.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <20150128222225.GF14935@zion.uk.xensource.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Wei Liu <wei.liu2@citrix.com>
Cc: ufimtseva@gmail.com, andrew.cooper3@citrix.com, dario.faggioli@citrix.com, ian.jackson@eu.citrix.com, xen-devel@lists.xen.org, JBeulich@suse.com
List-Id: xen-devel@lists.xenproject.org

On Wed, 2015-01-28 at 22:22 +0000, Wei Liu wrote:
> On Wed, Jan 28, 2015 at 04:41:11PM +0000, Ian Campbell wrote:
> > On Fri, 2015-01-23 at 11:13 +0000, Wei Liu wrote:
> > > Disallow memory relocation when vNUMA is enabled, because relocated
> > > memory ends up off node. Further more, even if we dynamically expand
> > > node coverage in hvmloader, low memory and high memory may reside
> > > in different physical nodes, blindly relocating low memory to high
> > > memory gives us a sub-optimal configuration.
> > 
> > What are the downsides of doing this? Less flexible PCI passthrough/MMIO
> > hole sizing I think? Anything else?
> 
> Yes, PCI passthrough and MMIO hole size are affected, but not to the
> degree that they are unusable.  Going forward like this doesn't make
> thing worse than before I think.

> Memory relocation is already disabled if we're using QEMU upstream.

Is that a shortcoming which might get fixed?

Is this vnuma restriction something which could be fixed in the future?
 
> > Does some user doc somewhere need this adding?
> > 
> > (and now I think of it, the PoD vs. vnuma one too).
> > 
> 
> Maybe release note or xl manpage?

Manpage would be good. Perhaps in some vnuma docs on the wiki too.

> 
> Wei.
> 
> > Ian.