From: Wei Yang <richard.weiyang@gmail.com>
To: rppt@kernel.org, akpm@linux-foundation.org, izumi.taku@jp.fujitsu.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
david@kernel.org, yuan1.liu@intel.com,
Wei Yang <richard.weiyang@gmail.com>
Subject: [RFC Patch 0/3] mm/mm_init: fix and cleanup mirrored_kernelcore
Date: Tue, 23 Jun 2026 09:23:48 +0000 [thread overview]
Message-ID: <20260623092351.13031-1-richard.weiyang@gmail.com> (raw)
When reviewing patch set "mm/memory_hotplug: optimize zone contiguous check
when changing pfn range" [1], we notice mirrored_kernelcore introduced some
special case to handle.
While during the discussion and test, it shows current mirrored_kernelcore
implementation breaks other memmap_init() behavior:
* disturbs defer_init()
* some Movable zone range would be initialized twice
The reason is Zone Movable and Zone Normal overlaps and current logic doesn't
handle it well.
As Yuan shows in [2], physical overlapped zone seems not exist in practice. If
remove the possibility of overlapped zone, problem could be solved. And also
could benefit zone contiguous optimization, IIUC.
Patch [1]: remove the overlapped zone, which fix the above two problem
Patch [2]: remove overlap_memmap_init() as there is no overlapped zone, but
record current double initialize problem for reference
Patch [3]: remove absent pages calculation for mirrored_kernelcore
[1]: https://lore.kernel.org/all/20260520093457.3719960-1-yuan1.liu@intel.com/T/#u
[2]: https://lore.kernel.org/all/20260520093457.3719960-1-yuan1.liu@intel.com/T/#mb0bd07ffd562a5b029f0f07751e580ca339c5b51
Cc: "David Hildenbrand (Arm)" <david@kernel.org>
Cc: Yuan Liu <yuan1.liu@intel.com>
Wei Yang (3):
mm/mm_init: adjust overlapped zone for mirror memory too
mm/mm_init: remove overlap_memmap_init() as no overlapped zone
mm/mm_init: remove special handling absent pages for
mirrored_kernelcore
mm/mm_init.c | 58 ++--------------------------------------------------
1 file changed, 2 insertions(+), 56 deletions(-)
---
This series is based on one proposed fix for node_spanned_pages:
https://lore.kernel.org/linux-mm/20260622022403.16375-1-richard.weiyang@gmail.com/
--
2.34.1
next reply other threads:[~2026-06-23 9:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 9:23 Wei Yang [this message]
2026-06-23 9:23 ` [RFC Patch 1/3] mm/mm_init: adjust overlapped zone for mirror memory too Wei Yang
2026-06-23 9:23 ` [RFC Patch 2/3] mm/mm_init: remove overlap_memmap_init() as no overlapped zone Wei Yang
2026-06-23 9:23 ` [RFC Patch 3/3] mm/mm_init: remove special handling absent pages for mirrored_kernelcore Wei Yang
2026-06-25 6:36 ` [RFC Patch 0/3] mm/mm_init: fix and cleanup mirrored_kernelcore 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=20260623092351.13031-1-richard.weiyang@gmail.com \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=izumi.taku@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
--cc=yuan1.liu@intel.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
all inboxes | Powered by JetHome®