From: Mike Rapoport <rppt@kernel.org>
To: "Liu, Yuan1" <yuan1.liu@intel.com>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
Oscar Salvador <osalvador@suse.de>,
Wei Yang <richard.weiyang@gmail.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"Hu, Yong" <yong.hu@intel.com>,
"Zou, Nanhai" <nanhai.zou@intel.com>,
Tim Chen <tim.c.chen@linux.intel.com>,
"Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>,
"Chen, Yu C" <yu.c.chen@intel.com>,
"Deng, Pan" <pan.deng@intel.com>,
"Li, Tianyou" <tianyou.li@intel.com>,
Chen Zhang <zhangchen.kidd@jd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] mm/memory hotplug/unplug: Optimize zone contiguous check when changing pfn range
Date: Mon, 20 Apr 2026 17:03:28 +0300 [thread overview]
Message-ID: <aeYyMFKvR8MZO6Tq@kernel.org> (raw)
In-Reply-To: <MW4PR11MB6936E593C865F4E855CED602A3202@MW4PR11MB6936.namprd11.prod.outlook.com>
On Fri, Apr 17, 2026 at 06:34:50AM +0000, Liu, Yuan1 wrote:
>
> > >>> sashiko had several comments
> > >>> https://sashiko.dev/#/patchset/20260408031615.1831922-1-
> > >> yuan1.liu%40intel.com
> > >>>
> > >>> I skipped the ones related to hotplug, but in the mm_init part the
> > >> comment
> > >>> about zones that can have overlapping physical spans when mirrored
> > >>> kernelcore is enabled seems valid.
> > >
> > > Hi David & Mike
> > >
> > > I’ve spent some time working through these issues to better understand
> > them.
> > > For the overlapping physical spans(mirrored kernelcore), should I avoid
> > counting
> > > overlap_memmap_init in memmap_init_range in the next version?
> > > For example, change it as follows:
> > >
> > > +unsigned long __meminit
> > > +memmap_init_range(unsigned long size, int nid, unsigned long zone,
> > > + unsigned long start_pfn,
> > > + unsigned long zone_end_pfn,
> > > enum meminit_context context,
> > > struct vmem_altmap *altmap, int migratetype,
> > > bool isolate_pageblock)
> > > {
> > > unsigned long pfn, end_pfn = start_pfn + size;
> > > + unsigned long nr_init = 0;
> > > struct page *page;
> > >
> > > if (highest_memmap_pfn < end_pfn - 1)
> > > @@ -893,7 +897,7 @@ void __meminit memmap_init_range(unsigned long size,
> > int nid, unsigned long zone
> > > if (zone == ZONE_DEVICE) {
> > > if (!altmap)
> > > - return;
> > > + return 0;
> > >
> > > if (start_pfn == altmap->base_pfn)
> > > start_pfn += altmap->reserve;
> > > @@ -911,6 +915,7 @@ void __meminit memmap_init_range(unsigned long size,
> > int nid, unsigned long zone
> > > if (defer_init(nid, pfn, zone_end_pfn)) {
> > > deferred_struct_pages = true;
> > > + nr_init += end_pfn - pfn;
> >
> > It's confusing. Could the remaining range also include overlapping inits?
> >
> > Maybe the whole "skip overlapping init" should actually be handled on a
> > higher level?
> >
> > I guess we'd want to skip any memblock_is_mirror(r) regions entirely.
> >
> > @Mike?
>
> Hi Mike
>
> David suggested moving the overlap handling to a higher level and
> skipping memblock_is_mirror() regions entirely. I think this makes sense.
>
> Would this work for you, or do you have a different preference?
Looks about right :)
> Something like this
> static void __init memmap_init(void)
> {
> ...
> for_each_mem_pfn_range(i, MAX_NUMNODES, &start_pfn, &end_pfn, &nid) {
> struct pglist_data *node = NODE_DATA(nid);
> bool is_mirror = mirrored_kernelcore &&
> memblock_is_mirror(&memblock.memory.regions[i]);
I'd add a local memblock_region variable.
>
> for (j = 0; j < MAX_NR_ZONES; j++) {
> ...
> if (is_mirror && j == ZONE_MOVABLE)
> continue;
>
> memmap_init_zone_range(zone, start_pfn, end_pfn,
> &hole_pfn);
> Best Regards,
> Liu, Yuan1
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-04-20 14:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-08 3:16 Yuan Liu
2026-04-08 7:36 ` David Hildenbrand (Arm)
2026-04-08 12:29 ` Liu, Yuan1
2026-04-08 12:31 ` David Hildenbrand (Arm)
2026-04-08 12:37 ` Liu, Yuan1
2026-04-09 14:40 ` Mike Rapoport
2026-04-09 15:08 ` David Hildenbrand (Arm)
2026-04-14 7:06 ` Liu, Yuan1
2026-04-14 9:24 ` David Hildenbrand (Arm)
2026-04-17 6:34 ` Liu, Yuan1
2026-04-17 9:00 ` David Hildenbrand (Arm)
2026-04-17 9:28 ` Liu, Yuan1
2026-04-20 14:03 ` Mike Rapoport [this message]
2026-04-21 0:00 ` Liu, Yuan1
2026-04-13 13:06 ` Wei Yang
2026-04-13 18:24 ` David Hildenbrand (Arm)
2026-04-14 2:12 ` Wei Yang
2026-04-14 9:32 ` David Hildenbrand (Arm)
2026-04-15 2:30 ` Wei Yang
2026-04-15 9:11 ` David Hildenbrand (Arm)
2026-04-16 2:23 ` Wei Yang
2026-04-16 7:15 ` David Hildenbrand (Arm)
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=aeYyMFKvR8MZO6Tq@kernel.org \
--to=rppt@kernel.org \
--cc=david@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nanhai.zou@intel.com \
--cc=osalvador@suse.de \
--cc=pan.deng@intel.com \
--cc=qiuxu.zhuo@intel.com \
--cc=richard.weiyang@gmail.com \
--cc=tianyou.li@intel.com \
--cc=tim.c.chen@linux.intel.com \
--cc=yong.hu@intel.com \
--cc=yu.c.chen@intel.com \
--cc=yuan1.liu@intel.com \
--cc=zhangchen.kidd@jd.com \
/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