Lines Matching refs:memory
4 * linux/mm/memory.c
34 * 05.04.94 - Multi-page memory management added for v1.1.
71 #include <linux/memory-tiers.h>
127 * that high_memory defines the upper bound on direct map memory, then end
187 * has been handled earlier when unmapping all the memory regions.
575 * VM_MIXEDMAP mappings can likewise contain memory with or without "struct
741 * memory so the entry shouldn't point to a filebacked page.
1311 * when the child accesses the memory range.
1688 * memory too. Come back again if we didn't do everything.
1852 * unmap_vmas - unmap a range of memory covered by a list of vma's
2493 * maps a range of physical memory into the requested pages. the old
2648 * remap_pfn_range - remap kernel memory to userspace
2651 * @pfn: page frame number of kernel physical memory address
2676 * vm_iomap_memory - remap memory to userspace
2678 * @start: start of the physical memory to be mapped
2682 * driver just needs to give us the physical memory range to be mapped,
2694 /* Check that the physical memory area passed in looks valid */
2699 * but we've historically allowed it because IO memory might
2915 * Scan a region of virtual memory, filling in page tables as necessary
2926 * Scan a region of virtual memory, calling a provided function on
4471 * The memory barrier inside __folio_mark_uptodate makes sure that
5198 * For memory tiering mode, cpupid of slow memory page is used
5944 * @vma: the memory mapping