Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.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 0/2] mm/mm_init: don't overlap zones with kernelcore=mirror
Date: Fri, 26 Jun 2026 11:11:25 +0300	[thread overview]
Message-ID: <aj40LRV2Rvw0Upw3@kernel.org> (raw)
In-Reply-To: <20260625073941.145014-1-rppt@kernel.org>

On Thu, Jun 25, 2026 at 10:39:38AM +0300, Mike Rapoport wrote:
> From: "Mike Rapoport (Microsoft)" <rppt@kernel.org>
> 
> Hi,
> 
> These patches make the behaviour of kernelcore= parameter uniform and
> treat mirror just as another way to size the zones and cleanup a weird
> part of the memory map initialization.

I'm queueing it for now in the memblock tree, will properly push after
merge window is closed.
    
> Mike Rapoport (Microsoft) (2):
>   mm/mm_init: don't overlap NORMAL and MOVABLE zones with kernelcore=mirror
>   mm/mm_init: drop overlap_memmap_init()
> 
>  mm/mm_init.c | 60 +++-------------------------------------------------
>  1 file changed, 3 insertions(+), 57 deletions(-)
> 
> 
> base-commit: 4549871118cf616eecdd2d939f78e3b9e1dddc48
> -- 
> 2.53.0
> 

-- 
Sincerely yours,
Mike.


      parent reply	other threads:[~2026-06-26  8:11 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)
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 ` Mike Rapoport [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=aj40LRV2Rvw0Upw3@kernel.org \
    --to=rppt@kernel.org \
    --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=richard.weiyang@gmail.com \
    --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