From mboxrd@z Thu Jan 1 00:00:00 1970 From: Juergen Gross Subject: Re: [PATCH 3/3] xen: eliminate scalability issues from initial mapping setup Date: Fri, 05 Sep 2014 10:03:34 +0200 Message-ID: <54096E56.3050809@suse.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; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54086244.7020601@citrix.com> Sender: linux-kernel-owner@vger.kernel.org To: David Vrabel , 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 09/04/2014 02:59 PM, 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. Yeah, there seem to be some bits missing... I'll add another patch to support a 4 level p2m scheme in the kernel. For the Xen tools I'll do it, too. Juergen