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/
Home Products Support Community News


[Xen-devel] x86-64's paging_init()

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] x86-64's paging_init()
From: "Jan Beulich" <jbeulich@xxxxxxxxxx>
Date: Thu, 31 Aug 2006 11:34:39 +0200
Delivery-date: Thu, 31 Aug 2006 02:34:24 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
While adding code to create the compatibility p2m table mappings it seemed
to me that the creation of the native ones is restricted to memory below
the 512G boundary - otherwise, additional L2 tables would need to be
allocated (currently other memory following the one L2 page getting
allocated would be blindly overwritten). While I realize that machines this
big aren't likely to be targeted by Xen at this point anyway (although the
direct map area explicitly provides for 1T), I'd still want this fixed if
someone confirms I'm not mis-reading something here (of if that's the case,
then I'd still need a good explanation, as then I'm likely screwing up the
compatibility table creation).


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>