The patch titled Subject: docs/vm: update ZONE_DEVICE memory model documentation has been added to the -mm tree. Its filename is mm-document-zone_device-memory-model-implications-fix.patch This patch should soon appear at http://ozlabs.org/~akpm/mmots/broken-out/mm-document-zone_device-memory-model-implications-fix.patch and later at http://ozlabs.org/~akpm/mmotm/broken-out/mm-document-zone_device-memory-model-implications-fix.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/process/submit-checklist.rst when testing your code *** The -mm tree is included into linux-next and is updated there every 3-4 working days ------------------------------------------------------ From: Dan Williams <dan.j.williams@xxxxxxxxx> Subject: docs/vm: update ZONE_DEVICE memory model documentation Mike notes that Sphinx needs a newline before the start of a bulleted list, and v10 of the subsection patch set changed the subsection size from an arch-variable 'PMD_SIZE' to a constant 2MB. Link: http://lkml.kernel.org/r/156109575458.1409767.1885676287099277666.stgit@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Signed-off-by: Dan Williams <dan.j.williams@xxxxxxxxx> Reported-by: Mike Rapoport <rppt@xxxxxxxxxxxxx> Cc: Jonathan Corbet <corbet@xxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- Documentation/vm/memory-model.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) --- a/Documentation/vm/memory-model.rst~mm-document-zone_device-memory-model-implications-fix +++ a/Documentation/vm/memory-model.rst @@ -205,10 +205,11 @@ subject to its memory ranges being expos hotplug api on memory block boundaries. The implementation relies on this lack of user-api constraint to allow sub-section sized memory ranges to be specified to :c:func:`arch_add_memory`, the top-half of -memory hotplug. Sub-section support allows for `PMD_SIZE` as the minimum -alignment granularity for :c:func:`devm_memremap_pages`. +memory hotplug. Sub-section support allows for 2MB as the cross-arch +common alignment granularity for :c:func:`devm_memremap_pages`. The users of `ZONE_DEVICE` are: + * pmem: Map platform persistent memory to be used as a direct-I/O target via DAX mappings. _ Patches currently in -mm which might be from dan.j.williams@xxxxxxxxx are mm-sparsemem-introduce-struct-mem_section_usage.patch mm-sparsemem-introduce-a-section_is_early-flag.patch mm-sparsemem-add-helpers-track-active-portions-of-a-section-at-boot.patch mm-hotplug-prepare-shrink_zone-pgdat_span-for-sub-section-removal.patch mm-sparsemem-convert-kmalloc_section_memmap-to-populate_section_memmap.patch mm-hotplug-kill-is_dev_zone-usage-in-__remove_pages.patch mm-kill-is_dev_zone-helper.patch mm-sparsemem-prepare-for-sub-section-ranges.patch mm-sparsemem-support-sub-section-hotplug.patch mm-document-zone_device-memory-model-implications.patch mm-document-zone_device-memory-model-implications-fix.patch mm-devm_memremap_pages-enable-sub-section-remap.patch libnvdimm-pfn-fix-fsdax-mode-namespace-info-block-zero-fields.patch libnvdimm-pfn-stop-padding-pmem-namespaces-to-section-alignment.patch mm-sparsemem-cleanup-section-number-data-types.patch