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] paging

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] paging
From: PUCCETTI Armand <armand.puccetti@xxxxxx>
Date: Wed, 02 Aug 2006 17:55:28 +0200
Delivery-date: Wed, 02 Aug 2006 08:55:13 -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 (X11/20060615)
I have a few easy questions about the xen code doing paging on AMD64.

How is the page translation function virt-to-phys (AMD64 arch programmer manual, page 147)
implemented ? Refining,

- In file /xen/include/asm-x86/page.h: what are the functions lXe_get_pfn, lXe_get_intpte, lXe_get_paddr, lXe_get_page, lXe_from_paddr (for X=1,..4) doing?

- One set of functions puzzles me: l4e_to_l3e, l3e_to_l2e and l2e_to_l1e. The comment says "Pagetable walking"... but what does this mean? do they help to move from one page map to another?

- In what variables are the real page tables (l4 to l1) stored?

- Does the code implement only long-mode page translation for AMD64?

- Is there anything explaining page.h, page_alloc.c and mm.c ?....

thanks and sorry for the trivial questions.


Xen-devel mailing list

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