Searched refs:ZONE_DEVICE (Results 1 – 11 of 11) sorted by relevance
185 ZONE_DEVICE chapter187 The `ZONE_DEVICE` facility builds upon `SPARSEMEM_VMEMMAP` to offer189 address ranges. The "device" aspect of `ZONE_DEVICE` relates to the fact192 to keep the memory pinned for active use. `ZONE_DEVICE`, via201 optionally collected into memory blocks, `ZONE_DEVICE` users have a need203 `ZONE_DEVICE` memory is never marked online it is subsequently never211 The users of `ZONE_DEVICE` are:216 * 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
290 zone = &NODE_DATA(nid)->node_zones[ZONE_DEVICE]; in memremap_pages()303 memmap_init_zone_device(&NODE_DATA(nid)->node_zones[ZONE_DEVICE], in memremap_pages()
650 config ZONE_DEVICE config681 depends on ZONE_DEVICE
480 if (zone_idx(zone) == ZONE_DEVICE) in __remove_zone()
5897 if (zone == ZONE_DEVICE) { in memmap_init_zone()5960 if (WARN_ON_ONCE(!pgmap || zone_idx(zone) != ZONE_DEVICE)) in memmap_init_zone_device()
48 select DEV_PAGEMAP_OPS if (ZONE_DEVICE && !FS_DAX_LIMITED)66 depends on ZONE_DEVICE
81 depends on ZONE_DEVICE
163 depends on ZONE_DEVICE
410 ZONE_DEVICE, enumerator
958 return page_zonenum(page) == ZONE_DEVICE; in is_zone_device_page()
