All of lore.kernel.org
 help / color / mirror / Atom feed
From: Muchun Song <muchun.song@linux.dev>
To: Muchun Song <songmuchun@bytedance.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.org>,
	Oscar Salvador <osalvador@suse.de>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Mike Rapoport <rppt@kernel.org>, Lorenzo Stoakes <ljs@kernel.org>,
	"Liam R . Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@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
Subject: Re: [PATCH v3 4/4] mm/mm_init: Fix pageblock migratetype for ZONE_DEVICE compound pages
Date: Tue, 21 Apr 2026 17:31:36 +0800	[thread overview]
Message-ID: <67CABBD2-FA75-40D0-909D-9B6A523CCC8C@linux.dev> (raw)
In-Reply-To: <20260421022044.1217503-5-songmuchun@bytedance.com>



> On Apr 21, 2026, at 10:20, Muchun Song <songmuchun@bytedance.com> wrote:
> 
> The memmap_init_zone_device() function only initializes the migratetype
> of the first pageblock of a compound page. If the compound page size
> exceeds pageblock_nr_pages (e.g., 1GB hugepages with 2MB pageblocks),
> subsequent pageblocks in the compound page remain uninitialized.
> 
> Move the migratetype initialization out of __init_zone_device_page()
> and into a separate pageblock_migratetype_init_range() function. This
> iterates over the entire PFN range of the memory, ensuring that all
> pageblocks are correctly initialized.
> 
> Fixes: c4386bd8ee3a ("mm/memremap: add ZONE_DEVICE support for compound pages")
> Signed-off-by: Muchun Song <songmuchun@bytedance.com>
> Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
> mm/mm_init.c | 43 ++++++++++++++++++++++++++++---------------
> 1 file changed, 28 insertions(+), 15 deletions(-)
> 
> diff --git a/mm/mm_init.c b/mm/mm_init.c
> index f9f8e1af921c..e2d8eae23aa3 100644
> --- a/mm/mm_init.c
> +++ b/mm/mm_init.c
> @@ -674,6 +674,19 @@ static inline void fixup_hashdist(void)
> static inline void fixup_hashdist(void) {}
> #endif /* CONFIG_NUMA */
> 
> +static __meminit void pageblock_migratetype_init_range(unsigned long pfn,
> +       unsigned long nr_pages,
> +       int migratetype)
> +{
> + 	unsigned long end = pfn + nr_pages;
> +
> + 	for (pfn = pageblock_align(pfn); pfn < end; pfn += pageblock_nr_pages) {
> + 		init_pageblock_migratetype(pfn_to_page(pfn), migratetype, false);
> + 		if (IS_ALIGNED(pfn, PAGES_PER_SECTION))
> + 			cond_resched();
> + 	}
> +}

I found a positive comment from AI review:

This trigger a -Wunused-function warning when CONFIG_ZONE_DEVICE is
disabled.

I'll fix it in the next version.

Thanks.



      parent reply	other threads:[~2026-04-21  9:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-21  2:20 [PATCH v3 0/4] mm: Fix vmemmap optimization accounting and initialization Muchun Song
2026-04-21  2:20 ` [PATCH v3 1/4] mm/sparse-vmemmap: Fix vmemmap accounting underflow Muchun Song
2026-04-21  3:45   ` Oscar Salvador
2026-04-21  2:20 ` [PATCH v3 2/4] mm/sparse-vmemmap: Pass @pgmap argument to memory deactivation paths Muchun Song
2026-04-21  3:55   ` Oscar Salvador
2026-04-21  4:01     ` Muchun Song
2026-04-21  2:20 ` [PATCH v3 3/4] mm/sparse-vmemmap: Fix DAX vmemmap accounting with optimization Muchun Song
2026-04-21  4:00   ` Oscar Salvador
2026-04-21  2:20 ` [PATCH v3 4/4] mm/mm_init: Fix pageblock migratetype for ZONE_DEVICE compound pages Muchun Song
2026-04-21  4:15   ` Oscar Salvador
2026-04-21  6:54     ` Muchun Song
2026-04-21  7:29       ` Oscar Salvador
2026-04-21  9:31   ` Muchun Song [this message]

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=67CABBD2-FA75-40D0-909D-9B6A523CCC8C@linux.dev \
    --to=muchun.song@linux.dev \
    --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=npiggin@gmail.com \
    --cc=osalvador@suse.de \
    --cc=rppt@kernel.org \
    --cc=songmuchun@bytedance.com \
    --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 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.