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] Question about Dom0 page table operations

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] Question about Dom0 page table operations
From: "zhujun" <zhujun@xxxxxxxxxxxxxx>
Date: Wed, 15 Jul 2009 23:50:02 +0800
Delivery-date: Wed, 15 Jul 2009 08:51:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcoFY+pL2cM8bh6eRI+cz+PwFLYxdQ==


         I am writing a driver for Dom0 to access DomU’s memory and encounter a problem to operate dom0’s page table. In my implementation, I have a pmd entry, which points to a L1 page table(A). Then this L1 page table(A)’s address is kept, and the same pmd points to another L1 page table(B) using set_pmd. But, when I use the former L1 page table(A) again using set_pmd, my code does not work! Also I know xen puts the former L1 page table’e type when the new L1 page table(B) was set. Any other considerations? How can I operate Dom 0’s process page table correctly?




Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Question about Dom0 page table operations, zhujun <=