From: Muchun Song <songmuchun@bytedance.com>
To: Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Muchun Song <muchun.song@linux.dev>,
Oscar Salvador <osalvador@suse.de>,
Michael Ellerman <mpe@ellerman.id.au>,
Madhavan Srinivasan <maddy@linux.ibm.com>
Cc: Lorenzo Stoakes <ljs@kernel.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <chleroy@kernel.org>,
aneesh.kumar@linux.ibm.com, joao.m.martins@oracle.com,
linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
Muchun Song <songmuchun@bytedance.com>
Subject: [PATCH v8 0/6] mm: Fix vmemmap optimization accounting and initialization
Date: Tue, 28 Apr 2026 16:18:49 +0800 [thread overview]
Message-ID: <20260428081855.1249045-1-songmuchun@bytedance.com> (raw)
The series fixes several bugs in vmemmap optimization, mainly around
incorrect page accounting and memmap initialization in DAX and memory
hotplug paths. It also fixes pageblock migratetype initialization and
struct page initialization for ZONE_DEVICE compound pages.
Patches 1-4 fix vmemmap accounting issues. Patch 1 fixes an accounting
underflow in the section activation failure path by moving vmemmap page
accounting into the lower-level allocation and freeing helpers. Patch 2
fixes incorrect altmap passing in the memory hotplug error path. Patch 3
passes pgmap through memory deactivation paths so the teardown side can
determine whether vmemmap optimization was in effect. Patch 4 uses that
information to account the optimized DAX vmemmap size correctly.
Patches 5-6 fix initialization issues in mm/mm_init. One makes sure all
pageblocks in ZONE_DEVICE compound pages get their migratetype
initialized. The other fixes a case where DAX memory hotplug reuses an
unoptimized early-section memmap while compound_nr_pages() still assumes
vmemmap optimization, leaving tail struct pages uninitialized.
Changes in v8:
- In patch 4, move VM_WARN_ON_ONCE(nr_pages > PAGES_PER_SECTION) to the
top of section_nr_vmemmap_pages().
- In patch 4, add Acked-by from David Hildenbrand.
Muchun Song (6):
mm/sparse-vmemmap: Fix vmemmap accounting underflow
mm/memory_hotplug: Fix incorrect altmap passing in error path
mm/sparse-vmemmap: Pass @pgmap argument to memory deactivation paths
mm/sparse-vmemmap: Fix DAX vmemmap accounting with optimization
mm/mm_init: Fix pageblock migratetype for ZONE_DEVICE compound pages
mm/mm_init: Fix uninitialized struct pages for ZONE_DEVICE
arch/arm64/mm/mmu.c | 5 +--
arch/loongarch/mm/init.c | 5 +--
arch/powerpc/mm/mem.c | 5 +--
arch/riscv/mm/init.c | 5 +--
arch/s390/mm/init.c | 5 +--
arch/x86/mm/init_64.c | 5 +--
include/linux/memory_hotplug.h | 8 +++--
mm/memory_hotplug.c | 13 ++++----
mm/memremap.c | 4 +--
mm/mm_init.c | 47 ++++++++++++++++-----------
mm/sparse-vmemmap.c | 58 ++++++++++++++++++++++++++--------
11 files changed, 105 insertions(+), 55 deletions(-)
base-commit: 39704f00f747aba3144289870b5fd8ac230a9aaf
--
2.20.1
next reply other threads:[~2026-04-28 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 8:18 Muchun Song [this message]
2026-04-28 8:18 ` [PATCH v8 1/6] mm/sparse-vmemmap: Fix vmemmap accounting underflow Muchun Song
2026-04-28 8:18 ` [PATCH v8 2/6] mm/memory_hotplug: Fix incorrect altmap passing in error path Muchun Song
2026-04-28 8:18 ` [PATCH v8 3/6] mm/sparse-vmemmap: Pass @pgmap argument to memory deactivation paths Muchun Song
2026-04-28 8:18 ` [PATCH v8 4/6] mm/sparse-vmemmap: Fix DAX vmemmap accounting with optimization Muchun Song
2026-04-28 8:18 ` [PATCH v8 5/6] mm/mm_init: Fix pageblock migratetype for ZONE_DEVICE compound pages Muchun Song
2026-04-28 8:18 ` [PATCH v8 6/6] mm/mm_init: Fix uninitialized struct pages for ZONE_DEVICE Muchun Song
2026-04-28 13:48 ` [PATCH v8 0/6] mm: Fix vmemmap optimization accounting and initialization Andrew Morton
2026-04-28 14:22 ` Liam R. Howlett
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=20260428081855.1249045-1-songmuchun@bytedance.com \
--to=songmuchun@bytedance.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=chleroy@kernel.org \
--cc=david@kernel.org \
--cc=joao.m.martins@oracle.com \
--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=osalvador@suse.de \
--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