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 |
139 ZONE_DEVICE chapter141 The `ZONE_DEVICE` facility builds upon `SPARSEMEM_VMEMMAP` to offer143 address ranges. The "device" aspect of `ZONE_DEVICE` relates to the fact146 to keep the memory pinned for active use. `ZONE_DEVICE`, via155 optionally collected into memory blocks, `ZONE_DEVICE` users have a need157 `ZONE_DEVICE` memory is never marked online it is subsequently never165 The users of `ZONE_DEVICE` are:170 * 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
281 zone = &NODE_DATA(nid)->node_zones[ZONE_DEVICE]; in pagemap_range()295 memmap_init_zone_device(&NODE_DATA(nid)->node_zones[ZONE_DEVICE], in pagemap_range()
781 config ZONE_DEVICE config811 depends on ZONE_DEVICE
6518 if (zone == ZONE_DEVICE) { in memmap_init_range()6571 if (WARN_ON_ONCE(!pgmap || zone_idx(zone) != ZONE_DEVICE)) in memmap_init_zone_device()
480 ZONE_DEVICE, enumerator977 return zone_idx(zone) == ZONE_DEVICE; in zone_is_zone_device()
1137 return page_zonenum(page) == ZONE_DEVICE; in is_zone_device_page()
82 depends on ZONE_DEVICE
49 select DEV_PAGEMAP_OPS if (ZONE_DEVICE && !FS_DAX_LIMITED)82 depends on ZONE_DEVICE
166 depends on ZONE_DEVICE
300 depends on X86 && ZONE_DEVICE
502 files or ZONE_DEVICE memory can be problematic, although only really relevant
