Searched refs:ZONE_DEVICE (Results 1 – 13 of 13) sorted by relevance
37 | pte_devmap | Tests a ZONE_DEVICE mapped PTE |57 | pte_mkdevmap | Creates a ZONE_DEVICE mapped PTE |107 | pmd_devmap | Tests a ZONE_DEVICE mapped PMD |127 | pmd_mkdevmap | Creates a ZONE_DEVICE mapped PMD |177 | pud_devmap | Tests a ZONE_DEVICE mapped PUD |191 | pud_mkdevmap | Creates a ZONE_DEVICE mapped PUD |
180 ZONE_DEVICE chapter182 The `ZONE_DEVICE` facility builds upon `SPARSEMEM_VMEMMAP` to offer184 address ranges. The "device" aspect of `ZONE_DEVICE` relates to the fact187 to keep the memory pinned for active use. `ZONE_DEVICE`, via196 optionally collected into memory blocks, `ZONE_DEVICE` users have a need198 `ZONE_DEVICE` memory is never marked online it is subsequently never206 The users of `ZONE_DEVICE` are:211 * hmm: Extend `ZONE_DEVICE` with `->page_fault()` and `->page_free()`
123 The second mechanism HMM provides is a new kind of ZONE_DEVICE memory that129 mechanisms. Here again, HMM only provides helpers, first to hotplug new ZONE_DEVICE
278 zone = &NODE_DATA(nid)->node_zones[ZONE_DEVICE]; in pagemap_range()292 memmap_init_zone_device(&NODE_DATA(nid)->node_zones[ZONE_DEVICE], in pagemap_range()
828 config ZONE_DEVICE config858 depends on ZONE_DEVICE
496 if (zone_idx(zone) == ZONE_DEVICE) in remove_pfn_range_from_zone()
6211 if (zone == ZONE_DEVICE) { in memmap_init_zone()6264 if (WARN_ON_ONCE(!pgmap || zone_idx(zone) != ZONE_DEVICE)) in memmap_init_zone_device()
51 select DEV_PAGEMAP_OPS if (ZONE_DEVICE && !FS_DAX_LIMITED)69 depends on ZONE_DEVICE
82 depends on ZONE_DEVICE
166 depends on ZONE_DEVICE
449 ZONE_DEVICE, enumerator
1124 return page_zonenum(page) == ZONE_DEVICE; in is_zone_device_page()
330 depends on X86 && ZONE_DEVICE