Lines Matching full:pagetable

10  * Xen allows guests to directly update the pagetable, in a controlled
11  * fashion.  In other words, the guest modifies the same pagetable
13  * a separate shadow pagetable.
21  * inserted directly into the pagetable.  When creating a new
26  * The other constraint is that all pages which make up a pagetable
28  * guest updates to the pagetable.  Xen strictly enforces this, and
29  * will disallow any pagetable update which will end up mapping a
30  * pagetable page RW, and will disallow using any writable page as a
31  * pagetable.
33  * Naively, when loading %cr3 with the base of a new pagetable, Xen
34  * would need to validate the whole pagetable before going on.
36  * pagetable, which enforces all the constraints on the pagetable even
101  * Note about cr3 (pagetable base) values:
218 	/* ptr may be ioremapped for 64-bit pagetable setup */  in xen_set_pmd_hyper()
401 	/* ptr may be ioremapped for 64-bit pagetable setup */  in xen_set_pud_hyper()
474  *  1. The only existing pagetable is the kernel's
476  *  3. It has no user pagetable attached to it
590  * (Yet another) pagetable walker.  This one is intended for pinning a
591  * pagetable.  This means that it walks a pagetable and calls the
593  * at every level.  It walks the entire pagetable, but it only bothers
689 		 * We need to hold the pagetable lock between the time  in xen_pin_page()
690 		 * we make the pagetable RO and when we actually pin  in xen_pin_page()
692 		 * attempt to update the pagetable by writing it,  in xen_pin_page()
697 		 * entire pagetable's worth of locks during the  in xen_pin_page()
706 		 * protected by the overall pagetable lock.  in xen_pin_page()
727    been used yet.  We need to make sure that its pagetable is all
788  * The init_mm pagetable is really pinned as soon as its created, but
919  * Another cpu may still have their %cr3 pointing at the pagetable, so
929 	/* Get the "official" set of cpus referring to our pagetable. */  in xen_drop_mm_ref()
965  * to it.  This means that all pagetable updates have to go via the
968  * Since we're pulling the pagetable down, we switch to use init_mm,
969  * unpin old process pagetable and mark it all read-write, which
973  * pagetable because of lazy tlb flushing.  This means we need need to
974  * switch all CPUs off this pagetable before we can unpin it.
1470 /* Early in boot, while setting up the initial pagetable, assume
1527    attached to a pinned pagetable. */
1685  * Set up the initial kernel pagetable.
1687  * We can construct this by grafting the Xen provided pagetable into
1765 	/* Make pagetable pieces RO */  in xen_setup_kernel_pagetable()
1809 	/* Our (by three pages) smaller Xen pagetable that we are using */  in xen_setup_kernel_pagetable()
2071 	   pagetable vsyscall mapping. */  in xen_set_fixmap()