Home
last modified time | relevance | path

Searched refs:ZONE_DEVICE (Results 1 – 15 of 15) sorted by relevance

/linux-6.6.21/Documentation/translations/zh_CN/mm/
Dmemory-model.rst109 ZONE_DEVICE chapter
111 `ZONE_DEVICE` 设施建立在 `SPARSEM_VMEMMAP` 之上,为设备驱动识别的物理地址范
112 围提供 `struct page` `mem_map` 服务。 `ZONE_DEVICE` 的 "设备" 方面与以下
114 是页面,以保持内存被“锁定”以便使用。 `ZONE_DEVICE` ,通过 :c:func:`devm_memremap_pages` ,
121 `ZONE_DEVICE` 用户需要更小的颗粒度来填充 `mem_map` 。鉴于 `ZONE_DEVICE`
127 `ZONE_DEVICE` 的用户是:
131 * hmm: 用 `->page_fault()` 和 `->page_free()` 事件回调扩展 `ZONE_DEVICE` ,
Dhmm.rst97 HMM 提供的第二种机制是一种新的 ZONE_DEVICE 内存,它允许为设备内存的每个页面分配一个
101 首先为设备内存热插拔新的 ZONE_DEVICE 内存,然后执行迁移。迁移内容和时间的策略决定留
/linux-6.6.21/Documentation/mm/
Darch_pgtable_helpers.rst35 | pte_devmap | Tests a ZONE_DEVICE mapped PTE |
59 | pte_mkdevmap | Creates a ZONE_DEVICE mapped PTE |
111 | pmd_devmap | Tests a ZONE_DEVICE mapped PMD |
135 | pmd_mkdevmap | Creates a ZONE_DEVICE mapped PMD |
185 | pud_devmap | Tests a ZONE_DEVICE mapped PUD |
199 | pud_mkdevmap | Creates a ZONE_DEVICE mapped PUD |
Dmemory-model.rst137 ZONE_DEVICE chapter
139 The `ZONE_DEVICE` facility builds upon `SPARSEMEM_VMEMMAP` to offer
141 address ranges. The "device" aspect of `ZONE_DEVICE` relates to the fact
144 to keep the memory pinned for active use. `ZONE_DEVICE`, via
153 optionally collected into memory blocks, `ZONE_DEVICE` users have a need
155 `ZONE_DEVICE` memory is never marked online it is subsequently never
163 The users of `ZONE_DEVICE` are:
168 * hmm: Extend `ZONE_DEVICE` with `->page_fault()` and `->page_free()`
Dphysical_memory.rst71 * ``ZONE_DEVICE`` represents memory residing on devices such as PMEM and GPU.
74 identified physical address ranges. ``ZONE_DEVICE`` is enabled with
Dhmm.rst121 The second mechanism HMM provides is a new kind of ZONE_DEVICE memory that
127 mechanisms. Here again, HMM only provides helpers, first to hotplug new ZONE_DEVICE
/linux-6.6.21/mm/
Dmemremap.c253 zone = &NODE_DATA(nid)->node_zones[ZONE_DEVICE]; in pagemap_range()
267 memmap_init_zone_device(&NODE_DATA(nid)->node_zones[ZONE_DEVICE], in pagemap_range()
Dmm_init.c867 if (zone == ZONE_DEVICE) { in memmap_init_range()
1076 if (WARN_ON_ONCE(!pgmap || zone_idx != ZONE_DEVICE)) in memmap_init_zone_device()
DKconfig686 def_bool MIGRATION && ZONE_DEVICE
1034 config ZONE_DEVICE config
1065 depends on ZONE_DEVICE
/linux-6.6.21/include/linux/
Dmmzone.h804 ZONE_DEVICE, enumerator
1101 return page_zonenum(page) == ZONE_DEVICE; in is_zone_device_page()
1468 return zone_idx(zone) == ZONE_DEVICE; in zone_is_zone_device()
/linux-6.6.21/fs/
DKconfig59 depends on ZONE_DEVICE || FS_DAX_LIMITED
92 depends on ZONE_DEVICE
/linux-6.6.21/drivers/nvdimm/
DKconfig65 depends on ZONE_DEVICE
/linux-6.6.21/drivers/pci/
DKconfig164 depends on ZONE_DEVICE
/linux-6.6.21/drivers/xen/
DKconfig337 depends on ZONE_DEVICE
/linux-6.6.21/Documentation/admin-guide/mm/
Dmemory-hotplug.rst621 files or ZONE_DEVICE memory can be problematic, although only really relevant