From: Muchun Song <songmuchun@bytedance.com>
To: Madhavan Srinivasan <maddy@linux.ibm.com>,
Mike Rapoport <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <chleroy@kernel.org>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R . Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Qi Zheng <qi.zheng@linux.dev>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Muchun Song <songmuchun@bytedance.com>,
muchun.song@linux.dev
Subject: [PATCH v2 2/6] mm/sparse-vmemmap: support device DAX in common vmemmap path
Date: Thu, 24 Sep 2026 15:52:55 +0800 [thread overview]
Message-ID: <20260924075259.2013039-3-songmuchun@bytedance.com> (raw)
In-Reply-To: <20260924075259.2013039-1-songmuchun@bytedance.com>
The common vmemmap population path cannot yet handle optimized Device DAX
mappings on its own. It uses pfn_to_zone() to find the shared tail page,
but Device DAX populates its vmemmap at runtime before the ZONE_DEVICE span
is initialized.
Teach the common path to use device_zone() for runtime optimized vmemmap
population while retaining pfn_to_zone() for early boot. This allows the
same path to support both early boot mappings and Device DAX.
The backing PFN supplied by the Device DAX-specific population path is no
longer used, allowing the redundant lookup and population code to be
removed later.
Signed-off-by: Muchun Song <songmuchun@bytedance.com>
---
v2:
- Expand comments around slab initialization to explain zone lookup and
page refcounting (suggested by Qi Zheng)
---
mm/sparse-vmemmap.c | 56 +++++++++++++++++++++++++--------------------
1 file changed, 31 insertions(+), 25 deletions(-)
diff --git a/mm/sparse-vmemmap.c b/mm/sparse-vmemmap.c
index 919c94a36346..cdcc93714a9a 100644
--- a/mm/sparse-vmemmap.c
+++ b/mm/sparse-vmemmap.c
@@ -208,18 +208,39 @@ static __meminit void *vmemmap_alloc_pte(unsigned long pfn, int node,
struct page *page;
const unsigned int order = pfn_to_section_compound_order(pfn);
- /*
- * Device DAX still relies on vmemmap_populate_compound_pages() for
- * head/first-tail allocation and tail-page reuse.
- */
if (!vmemmap_optimizable_pfn(pfn))
return vmemmap_alloc_block_buf(PAGE_SIZE, node, altmap);
- zone = pfn_to_zone(pfn, node);
+ /*
+ * Before slab is available, vmemmap optimization is used for early
+ * system RAM, whose zone can be determined from the PFN.
+ *
+ * Once slab is available, only ZONE_DEVICE memory reaches this
+ * optimized population path. Its zone span has not been initialized
+ * while its vmemmap is being populated, so pfn_to_zone() cannot be
+ * used. Obtain ZONE_DEVICE directly from the node instead.
+ */
+ zone = slab_is_available() ? device_zone(node) : pfn_to_zone(pfn, node);
page = vmemmap_shared_tail_page(order, zone);
if (!page)
return NULL;
+ /*
+ * During early vmemmap population, the shared tail vmemmap backing
+ * page is allocated from memblock before its struct page can safely
+ * participate in page refcounting. Therefore, no reference can be
+ * held for each shared PTE mapping, and the mappings must be unshared
+ * before the vmemmap is depopulated.
+ *
+ * Once slab is available, the shared backing page is allocated from
+ * the buddy allocator and can be refcounted. Hold one reference for
+ * each shared PTE mapping. The architecture vmemmap teardown drops
+ * the reference through __free_pages() when removing the mapping,
+ * preventing the backing page from being freed while it is shared.
+ */
+ if (slab_is_available())
+ get_page(page);
+
return page_address(page);
}
@@ -231,27 +252,12 @@ static pte_t * __meminit vmemmap_pte_populate(pmd_t *pmd, unsigned long addr, in
if (pte_none(ptep_get(pte))) {
pte_t entry;
+ void *p = vmemmap_alloc_pte(pfn, node, altmap);
- if (ptpfn == (unsigned long)-1) {
- void *p = vmemmap_alloc_pte(pfn, node, altmap);
-
- if (!p)
- return NULL;
- ptpfn = PHYS_PFN(__pa(p));
- } else {
- /*
- * When a PTE/PMD entry is freed from the init_mm
- * there's a free_pages() call to this page allocated
- * above. Thus this get_page() is paired with the
- * put_page_testzero() on the freeing path.
- * This can only called by certain ZONE_DEVICE path,
- * and through vmemmap_populate_compound_pages() when
- * slab is available.
- */
- if (slab_is_available())
- get_page(pfn_to_page(ptpfn));
- }
- entry = pfn_pte(ptpfn, PAGE_KERNEL);
+ if (!p)
+ return NULL;
+
+ entry = pfn_pte(PHYS_PFN(__pa(p)), PAGE_KERNEL);
set_pte_at(&init_mm, addr, pte, entry);
} else if (WARN_ON_ONCE(vmemmap_optimizable_pfn(pfn)))
return NULL;
--
2.54.0
next prev parent reply other threads:[~2026-09-24 7:58 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 7:52 [PATCH v2 0/6] mm: Unify device DAX and HugeTLB vmemmap population paths Muchun Song
2026-09-24 7:52 ` [PATCH v2 1/6] mm/sparse-vmemmap: drop VMEMMAP_POPULATE_DAX Muchun Song
2026-09-24 7:52 ` Muchun Song [this message]
2026-09-28 1:49 ` [PATCH v2 2/6] mm/sparse-vmemmap: support device DAX in common vmemmap path Qi Zheng
2026-09-24 7:52 ` [PATCH v2 3/6] mm/sparse-vmemmap: drop Device DAX-specific population path Muchun Song
2026-09-24 7:52 ` [PATCH v2 4/6] mm/sparse-vmemmap: remove the unused ptpfn argument Muchun Song
2026-09-24 7:52 ` [PATCH v2 5/6] mm/sparse-vmemmap: open-code vmemmap_populate_address() Muchun Song
2026-09-24 7:52 ` [PATCH v2 6/6] mm/mm_init: add zone mismatch warning during page init Muchun Song
2026-09-28 1:59 ` Qi Zheng
2026-09-28 12:44 ` [PATCH v2 0/6] mm: Unify device DAX and HugeTLB vmemmap population paths David Hildenbrand (Arm)
2026-09-28 13:49 ` Muchun Song
2026-09-28 17:43 ` Ritesh Harjani
2026-09-28 19:03 ` David Hildenbrand (Arm)
2026-09-29 0:51 ` Muchun Song
2026-09-29 0:57 ` Muchun Song
2026-09-29 1:57 ` Ritesh Harjani
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260924075259.2013039-3-songmuchun@bytedance.com \
--to=songmuchun@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=chleroy@kernel.org \
--cc=david@kernel.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ljs@kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mhocko@suse.com \
--cc=mpe@ellerman.id.au \
--cc=muchun.song@linux.dev \
--cc=npiggin@gmail.com \
--cc=qi.zheng@linux.dev \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox