[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] Xeno Linux never pins L1 tables ?
- To: Satya <satyakiran@xxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
- From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
- Date: Tue, 16 Oct 2007 15:47:31 +0100
- Delivery-date: Tue, 16 Oct 2007 07:48:17 -0700
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
- Thread-index: AcgQA3q5uRXa2Hv2Edy34gAX8io7RQ==
- Thread-topic: [Xen-devel] Xeno Linux never pins L1 tables ?
PTEs end up pinned by virtue of being referenced via a pinned PGD. When a PGD is pinned Xen walks the whole pagetable structure.
-- Keir
On 16/10/07 15:44, "Satya" <satyakiran@xxxxxxxxx> wrote:
hi,
I'm developing my own 32-bit (no PAE) paravirtualized kernel for xen with Mini-OS as a starting point. I am currently working on process page table support (equivalent of arch/i386/mm/pgtable-xen.c) and mostly following Linux for the moment. I noticed that linux-2.6.18-xen never pins an L1 table (a pte), yet __pgd_pin() walks the page directory and gives up write access on the kernel mappings of pte pages and only pins the pgd page. How do set_pte() and set_pte_at() macros work if they are writing directly to the page table entires ? do we fault in the kernel to handle this ?!
thanks,
satya.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
