From: Andrew Cooper Subject: Re: [Xen-devel] [PATCH 3/3] xen: eliminate scalability issues from initial mapping setup Date: Thu, 4 Sep 2014 14:02:54 +0100 Message-ID: <540862FE.7070108@citrix.com> References: <1409834326-29287-1-git-send-email-jgross@suse.com> <1409834326-29287-4-git-send-email-jgross@suse.com> <54086244.7020601@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54086244.7020601@citrix.com> Sender: linux-kernel-owner@vger.kernel.org To: David Vrabel , Juergen Gross , linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com, konrad.wilk@oracle.com, boris.ostrovsky@oracle.com, jbeulich@suse.com List-Id: xen-devel@lists.xenproject.org On 04/09/14 13:59, David Vrabel wrote: > On 04/09/14 13:38, Juergen Gross wrote: >> Direct Xen to place the initial P->M table outside of the initial >> mapping, as otherwise the 1G (implementation) / 2G (theoretical) >> restriction on the size of the initial mapping limits the amount >> of memory a domain can be handed initially. > The three level p2m limits memory to 512 GiB on x86-64 but this patch > doesn't seem to address this limit and thus seems a bit useless to me. > > David Any increase of the p2m beyond 3 levels will need to come with substantial libxc changes first. 3 level p2ms are hard coded throughout all the PV build and migrate code. ~Andrew