From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Mike Rapoport <rppt@kernel.org>, linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Taku Izumi <izumi.taku@jp.fujitsu.com>,
Wei Yang <richard.weiyang@gmail.com>,
Yuan Liu <yuan1.liu@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] mm/mm_init: drop overlap_memmap_init()
Date: Tue, 7 Jul 2026 15:45:58 +0200 [thread overview]
Message-ID: <a70a5aea-012d-4bfa-8be9-3f8ba55c53f8@kernel.org> (raw)
In-Reply-To: <20260630072212.624305-3-rppt@kernel.org>
On 6/30/26 09:22, Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
>
> When ZONE_NORMAL and ZONE_MOVABLE could overlap because kernelcore=mirror
> didn't reduce the span of ZONE_NORMAL, initialization of the memory map had
> to skip overlapping pages during initialization of ZONE_MOVABLE to avoid
> double initialization of the same struct pages.
>
> Since kernelcore=mirror works now the same way as other variants of
> kernelcore=/movablecore=, and adjusts the span of ZONE_NORMAL, there can't
> be an overlap between ZONE_NORMAL and ZONE_MOVABLE.
>
> Remove overlap_memmap_init().
>
> Co-developed-by: Wei Yang <richard.weiyang@gmail.com>
> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
> Signed-off-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
> ---
Reviewed-by: David Hildenbrand (Arm) <david@kernel.org>
--
Cheers,
David
prev parent reply other threads:[~2026-07-07 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 7:22 [PATCH v2 0/2] mm/mm_init: don't overlap zones with kernelcore=mirror Mike Rapoport
2026-06-30 7:22 ` [PATCH v2 1/2] mm/mm_init: don't overlap NORMAL and MOVABLE " Mike Rapoport
2026-07-07 13:45 ` David Hildenbrand (Arm)
2026-06-30 7:22 ` [PATCH v2 2/2] mm/mm_init: drop overlap_memmap_init() Mike Rapoport
2026-07-07 13:45 ` David Hildenbrand (Arm) [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=a70a5aea-012d-4bfa-8be9-3f8ba55c53f8@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=izumi.taku@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=richard.weiyang@gmail.com \
--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 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.