From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,muchun.song@linux.dev,akpm@linux-foundation.org
Subject: [to-be-updated] mm-hugetlb_vmemmap-unify-writable-vmemmap-page-preparation.patch removed from -mm tree
Date: Fri, 06 Nov 2026 19:49:49 -0800 [thread overview]
Message-ID: <20261107034950.59C391F008A1@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm: hugetlb_vmemmap: unify writable vmemmap page preparation
has been removed from the -mm tree. Its filename was
mm-hugetlb_vmemmap-unify-writable-vmemmap-page-preparation.patch
This patch was dropped because an updated version will be issued
------------------------------------------------------
From: Muchun Song <muchun.song@linux.dev>
Subject: mm: hugetlb_vmemmap: unify writable vmemmap page preparation
Date: Wed, 04 Nov 2026 10:35:03 +0800
Installing a writable vmemmap page requires consuming a replacement page,
copying the current contents into it and making the copy visible before
publishing the new mapping. HVO currently splits this sequence between
the page-table walker and its caller depending on the remap path.
Centralize the sequence in the walker so all writable replacements follow
the same copy-and-publish protocol. This keeps page preparation with the
mapping update and removes path-specific handling from higher-level HVO
code.
No functional change intended.
Link: https://lore.kernel.org/20261104023510.260766-6-songmuchun@bytedance.com
Signed-off-by: Muchun Song <muchun.song@linux.dev>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Reviewed-by: Lance Yang <lance.yang@linux.dev>
Reviewed-by: Qi Zheng <qi.zheng@linux.dev>
Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
Tested-by: Andrew Morton <akpm@linux-foundation.org>
Link: https://lore.kernel.org/20261103224659.2865b9ff27d09994949edd78@linux-foundation.org
Reviewed-by: Oscar Salvador <osalvador@suse.de>
Cc: James Houghton <jthoughton@google.com>
Cc: David Hildenbrand <david@kernel.org>
Cc: Huacai Chen <chenhuacai@kernel.org>
---
mm/hugetlb_vmemmap.c | 40 +++++++++++++++++-----------------------
1 file changed, 17 insertions(+), 23 deletions(-)
--- a/mm/hugetlb_vmemmap.c~mm-hugetlb_vmemmap-unify-writable-vmemmap-page-preparation
+++ a/mm/hugetlb_vmemmap.c
@@ -199,6 +199,20 @@ static void free_vmemmap_page_list(struc
free_vmemmap_page(page);
}
+static struct page *vmemmap_dup_page_from_list(const struct page *src,
+ struct list_head *vmemmap_pages)
+{
+ struct page *dst = list_first_entry(vmemmap_pages, struct page, lru);
+
+ list_del(&dst->lru);
+ copy_page(page_address(dst), page_address(src));
+
+ /* Ensure updates to @dst page are visible before set_pte_at(). */
+ smp_wmb();
+
+ return dst;
+}
+
static void vmemmap_remap_pte(pte_t *pte, unsigned long addr,
struct vmemmap_remap_walk *walk)
{
@@ -211,16 +225,7 @@ static void vmemmap_remap_pte(pte_t *pte
VM_WARN_ON_ONCE(!PageHead((const struct page *)addr));
- head = list_first_entry(walk->vmemmap_pages, struct page, lru);
- list_del(&head->lru);
-
- /*
- * Makes sure that preceding stores to the page contents from
- * vmemmap_remap_free() become visible before the set_pte_at()
- * write.
- */
- smp_wmb();
-
+ head = vmemmap_dup_page_from_list(page, walk->vmemmap_pages);
entry = mk_pte(head, PAGE_KERNEL);
} else {
VM_WARN_ON_ONCE(!PageTail((const struct page *)addr));
@@ -253,15 +258,7 @@ static void vmemmap_restore_pte(pte_t *p
VM_WARN_ON_ONCE(PageHead((const struct page *)addr));
- dst = list_first_entry(walk->vmemmap_pages, struct page, lru);
- list_del(&dst->lru);
- copy_page(page_to_virt(dst), page_to_virt(src));
-
- /*
- * Makes sure that preceding stores to the page contents become visible
- * before the set_pte_at() write.
- */
- smp_wmb();
+ dst = vmemmap_dup_page_from_list(src, walk->vmemmap_pages);
set_pte_at(&init_mm, addr, pte, mk_pte(dst, PAGE_KERNEL));
}
@@ -499,7 +496,7 @@ static int __hugetlb_vmemmap_optimize_fo
unsigned long flags)
{
unsigned long vmemmap_start, vmemmap_end;
- struct page *vmemmap_head, *vmemmap_tail;
+ struct page *vmemmap_tail;
int nid, ret = 0;
VM_WARN_ON_ONCE_FOLIO(!folio_test_hugetlb(folio), folio);
@@ -531,9 +528,6 @@ static int __hugetlb_vmemmap_optimize_fo
goto out;
}
- vmemmap_head = list_first_entry(vmemmap_pages, struct page, lru);
- copy_page(page_to_virt(vmemmap_head), folio);
-
vmemmap_start = (unsigned long)&folio->page;
vmemmap_end = vmemmap_start + hugetlb_vmemmap_size(h);
_
Patches currently in -mm which might be from muchun.song@linux.dev are
mm-fix-missing-page-table-destructor-in-pagetable_free.patch
riscv-mm-fix-hotplug-page-table-destructor-handling.patch
riscv-mm-fix-missing-destructor-for-hotplug-pud-tables.patch
arm64-mm-fix-destructor-for-unconstructed-hotplug-page-tables.patch
mm-sparse-vmemmap-map-shared-vmemmap-tail-pages-as-read-only.patch
powerpc-mm-map-shared-vmemmap-tail-pages-as-read-only.patch
mm-hugetlb_vmemmap-remove-vmemmap_wrprotect_hvo.patch
mm-hugetlb_vmemmap-remove-hugetlb_vmemmap_optimize_bootmem_folios.patch
mm-generalize-kernel-pte-table-allocation.patch
mm-generalize-pmd-page-table-allocation.patch
mm-generalize-pud-page-table-allocation.patch
mm-remove-pagetable_dtor_free.patch
mm-remove-redundant-pagetable_dtor-calls.patch
mm-hugetlb_vmemmap-rename-vmemmap_remap_pte-to-vmemmap_optimize_pte.patch
mm-hugetlb_vmemmap-simplify-shared-tail-page-handling.patch
mm-hugetlb_vmemmap-move-alloc_vmemmap_page_list-next-to-its-free-helper.patch
mm-hugetlb_vmemmap-make-vmemmap-optimization-folio-oriented.patch
mm-hugetlb_vmemmap-make-vmemmap-restoration-folio-oriented.patch
mm-hugetlb_vmemmap-unify-vmemmap-range-restoration.patch
mm-hugetlb_vmemmap-make-vmemmap-pte-conversion-folio-oriented.patch
mm-hugetlb-fix-validation-of-unsupported-hugetlb-orders.patch
reply other threads:[~2026-11-07 3:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261107034950.59C391F008A1@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=mm-commits@vger.kernel.org \
--cc=muchun.song@linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.