Lines Matching refs:that
12 however, that this range contains small holes that are not accessible
20 whether it is possible to manually override that default.
30 helpers that allow the conversion from PFN to `struct page` and vice
40 In the FLATMEM memory model, there is a global `mem_map` array that
47 usable until the call to :c:func:`memblock_free_all` that hands all the
50 An architecture may free parts of the `mem_map` array that do not cover the
66 is the only memory model that supports several advanced features such
73 that contains `section_mem_map` that is, logically, a pointer to an
75 that aids the sections management. The section size and maximal number
77 `MAX_PHYSMEM_BITS` constants defined by each architecture that
79 physical address that an architecture supports, the
111 and uses high bits of a PFN to access the section that maps that page
116 page *vmemmap` pointer that points to a virtually contiguous array of
117 `struct page` objects. A PFN is an index to that array and the
118 offset of the `struct page` from `vmemmap` is the PFN of that
122 addresses that will map the physical pages containing the memory
123 map and make sure that `vmemmap` points to that range. In addition,
125 that will allocate the physical memory and create page tables for the
134 that is eventually passed to vmemmap_populate() through a long chain
144 that the page objects for these address ranges are never marked online,
145 and that a reference must be taken against the device, not just the page
152 for back referencing to the host device / driver that mapped the memory.
156 for smaller granularity of populating the `mem_map`. Given that