From mboxrd@z Thu Jan  1 00:00:00 1970
From: PUCCETTI Armand <armand.puccetti@cea.fr>
Subject: mm.c
Date: Fri, 21 Jul 2006 18:54:21 +0200
Message-ID: <44C106BD.6090307@cea.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

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