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] mm.c

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] mm.c
From: PUCCETTI Armand <armand.puccetti@xxxxxx>
Date: Fri, 21 Jul 2006 18:54:21 +0200
Delivery-date: Fri, 21 Jul 2006 09:53:59 -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
User-agent: Thunderbird 1.5.0.4 (X11/20060615)
I have a question about the xen code doing memory management on AMD64.

Could someone please explain me how page table walking functions (file page.h)
work? For instance, l4e_to_l3e.

As far as I understand, l4e_to_l3e turns an entry of level4 page table into a virtual address that points to a level3 page table? Is that ok? How is that done in details? Where are the real
page tables (l4 to l1) stored?

More generally, is there any doc explaining the details in page.h ?....

thanks!
Armand


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] mm.c, PUCCETTI Armand <=