Lines Matching full:page
26 page tables. Meaning that if the software page tables change, it is
28 Therefore when software page table changes occur, the kernel will
29 invoke one of the following flush methods _after_ the page table
35 any previous page table modification whatsoever will be
38 This is usually invoked when the kernel page tables are
45 any previous page table modifications for the address space
50 page table operations such as what happens during
58 interface must make sure that any previous page table
68 a suitably efficient method for removing multiple page
84 page table modification for address space 'vma->vm_mm' for
95 At the end of every page fault, this routine is invoked to tell
97 in the software page tables for address space "vma->vm_mm"
148 page table operations such as what happens during exit and exec.
157 page table operations such as what happens during fork.
174 a suitably efficient method for removing multiple page
189 The 'pfn' indicates the physical page frame (shift this value
221 has installed the page table entries. The second is invoked
222 before vunmap_range() deletes the page table entries.
247 other cases. Please keep in mind that fact that, for a given page
251 physical page into its address space, by implication the D-cache
253 maps this page at its virtual address.
255 ``void copy_user_page(void *to, void *from, unsigned long addr, struct page *page)``
256 ``void clear_user_page(void *to, unsigned long addr, struct page *page)``
266 of the same "color" as the user mapping of the page. Sparc64
270 user will ultimately have this page mapped, and the 'page'
271 parameter gives a pointer to the struct page of the target.
280 a) the kernel did write to a page that is in the page cache page
282 b) the kernel is about to read from a page cache page and user space
283 shared/writable mappings of this page potentially exist. Note
285 on any page found in the user address space and thus driver
290 This routine need only be called for page cache pages
293 handling vfs symlinks in the page cache need not call
296 The phrase "kernel writes to a page cache page" means, specifically,
298 page at the kernel virtual mapping of that page. It is important to
300 are visible to user space mappings of that page.
311 clear this bit when such a page first enters the pagecache.
316 page. See sparc64's flush_dcache_folio and update_mmu_cache_range
321 mapping returns %false, just mark the architecture private page
330 as did the cpu stores into the page to make it
334 ``void copy_to_user_page(struct vm_area_struct *vma, struct page *page,
336 ``void copy_from_user_page(struct vm_area_struct *vma, struct page *page,
349 ``void flush_anon_page(struct vm_area_struct *vma, struct page *page,
353 page, it calls this function (currently only
355 doesn't work for an anonymous page. The default
358 the cache of the page at vmaddr.
368 ``void flush_icache_page(struct vm_area_struct *vma, struct page *page)``
388 page. The design is to make this area safe to perform I/O on.