Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

vm_insert_page(9) [centos man page]

VM_INSERT_PAGE(9)					    Memory Management in Linux						 VM_INSERT_PAGE(9)

vm_insert_page - insert single page into user vma SYNOPSIS
int vm_insert_page(struct vm_area_struct * vma, unsigned long addr, struct page * page); ARGUMENTS
vma user vma to map to addr target user address of this page page source kernel page DESCRIPTION
This allows drivers to insert individual pages they've allocated into a user vma. The page has to be a nice clean _individual_ kernel allocation. If you allocate a compound page, you need to have marked it as such (__GFP_COMP), or manually just split the page up yourself (see split_page). NOTE! Traditionally this was done with "remap_pfn_range" which took an arbitrary page protection parameter. This doesn't allow that. Your vma protection will have to be set up correctly, which means that if you want a shared writable mapping, you'd better ask for a shared writable mapping! The page does not need to be reserved. Usually this function is called from f_op->mmap handler under mm->mmap_sem write-lock, so it can change vma->vm_flags. Caller must set VM_MIXEDMAP on vma if it wants to call this function from other places, for example from page-fault handler. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 VM_INSERT_PAGE(9)

Check Out this Related Man Page

mprotect(2)							   System Calls 						       mprotect(2)

mprotect - set protection of memory mapping SYNOPSIS
#include <sys/mman.h> int mprotect(void *addr, size_t len, int prot); DESCRIPTION
The mprotect() function changes the access protections on the mappings specified by the range [addr, addr + len), rounding len up to the next multiple of the page size as returned by sysconf(3C), to be that specified by prot. Legitimate values for prot are the same as those permitted for mmap(2) and are defined in <sys/mman.h> as: PROT_READ /* page can be read */ PROT_WRITE /* page can be written */ PROT_EXEC /* page can be executed */ PROT_NONE /* page can not be accessed */ When mprotect() fails for reasons other than EINVAL, the protections on some of the pages in the range [addr, addr + len) may have been changed. If the error occurs on some page at addr2, then the protections of all whole pages in the range [addr, addr2] will have been modi- fied. RETURN VALUES
Upon successful completion, mprotect() returns 0. Otherwise, it returns -1 and sets errno to indicate the error. ERRORS
The mprotect() function will fail if: EACCES The prot argument specifies a protection that violates the access permission the process has to the underlying memory object. EINVAL The len argument has a value equal to 0, or addr is not a multiple of the page size as returned by sysconf(3C). ENOMEM Addresses in the range [addr, addr + len) are invalid for the address space of a process, or specify one or more pages which are not mapped. The mprotect() function may fail if: EAGAIN The address range [addr, addr + len) includes one or more pages that have been locked in memory and that were mapped MAP_PRIVATE; prot includes PROT_WRITE; and the system has insufficient resources to reserve memory for the private pages that may be created. These private pages may be created by store operations in the now-writable address range. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ SEE ALSO
mmap(2), plock(3C), mlock(3C), mlockall(3C), sysconf(3C), attributes(5), standards(5) SunOS 5.11 12 Jan 1998 mprotect(2)
Man Page

Featured Tech Videos