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 1/2] mm/mm_init: don't overlap NORMAL and MOVABLE zones with kernelcore=mirror
Date: Thu, 25 Jun 2026 12:42:09 +0200 [thread overview]
Message-ID: <eba3da0f-cb01-4550-85a2-4696d0fbc194@kernel.org> (raw)
In-Reply-To: <20260625073941.145014-2-rppt@kernel.org>
On 6/25/26 09:39, Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
>
> When kernelcore or movablecore kernel parameters define size of the
> NORMAL and MOVABLE zones as percents of the total memory or by absolute
> value, ZONE_NORMAL is clamped at the beginning of ZONE_MOVABLE.
>
> However, when kernelcore=mirror the ZONE_NORMAL span is not changed but
> rather pages from ZONE_MOVABLE counted as absent in ZONE_NORMAL.
>
> Make the behaviour of kernelcore= parameter uniform and treat mirror
> just as another way to size the zones.
That sounds just about right to me.
Hard to imagine that any code would have relied on the old behavior.
Reviewed-by: David Hildenbrand (Arm) <david@kernel.org>
--
Cheers,
David
next prev parent reply other threads:[~2026-06-25 10:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 7:39 [PATCH 0/2] mm/mm_init: don't overlap zones with kernelcore=mirror Mike Rapoport
2026-06-25 7:39 ` [PATCH 1/2] mm/mm_init: don't overlap NORMAL and MOVABLE " Mike Rapoport
2026-06-25 10:42 ` David Hildenbrand (Arm) [this message]
2026-06-25 7:39 ` [PATCH 2/2] mm/mm_init: drop overlap_memmap_init() Mike Rapoport
2026-06-25 9:58 ` Wei Yang
2026-06-26 7:40 ` Mike Rapoport
2026-06-26 9:29 ` Wei Yang
2026-06-25 10:43 ` David Hildenbrand (Arm)
2026-06-26 8:11 ` [PATCH 0/2] mm/mm_init: don't overlap zones with kernelcore=mirror Mike Rapoport
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=eba3da0f-cb01-4550-85a2-4696d0fbc194@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox