Re: [PATCH v3 3/6] mm/sparse-vmemmap: drop Device DAX-specific population path

On Tue, Sep 29, 2026 at 01:32:28PM +0800, Muchun Song wrote:

The common vmemmap path selects the shared page for optimized mappings
itself, so Device DAX no longer needs vmemmap_populate_compound_pages()
to find a shared tail page and pass its backing PFN through the generic
population helpers.

Remove the Device DAX-specific population path and let section memmap
population always use vmemmap_populate(). The powerpc retains an
architecture-specific compound-page implementation, so select it directly
from radix__vmemmap_populate() for optimizable sections.

Signed-off-by: Muchun Song <redacted>
Acked-by: Qi Zheng <qi.zheng@linux.dev>
---

LGTM! Feel free to add:

Reviewed-by: Lance Yang <lance.yang@linux.dev>