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

[Xen-devel] P2M Top Level Page Table

To: xen-devel@xxxxxxxxxxxxxxxxxxx, "Tim Deegan" <Tim.Deegan@xxxxxxxxxxxxx>
Subject: [Xen-devel] P2M Top Level Page Table
From: "Huang2, Wei" <Wei.Huang2@xxxxxxx>
Date: Thu, 29 Mar 2007 11:05:41 -0500
Delivery-date: Thu, 29 Mar 2007 17:07:02 +0100
Envelope-to: Keir.Fraser@xxxxxxxxxxxx
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
Thread-index: AcdyHBl6ROin1Ah6Tnm0i91fEIxX9g==
Thread-topic: P2M Top Level Page Table
Current P2M table are allocated through alloc_domheap_pages(), which can potentially allocate memory with physical address > 4G under PAE mode. However, for top level P2M table (under PAE mode), its physical address should be below 4G because CR3 has only 32 bits. I noticed that mm.c relies on pae_l3_cache to solve this problem in make_cr3(). Do we plan to have similar solution for P2M table? Another solution might use xmalloc; but I just wonder whether it always returns memory below 4G.
 
Any though?
 
Thanks,
 
-Wei
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>