Devicetree
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
	linux-mm@kvack.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Saravana Kannan <saravanak@kernel.org>,
	Oreoluwa Babatunde <quic_obabatun@quicinc.com>,
	Wandun <chenwandun1@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 2/2] of: reserved_mem: allocate and map the reserved_mem array early
Date: Sat, 10 Oct 2026 12:01:26 +0200	[thread overview]
Message-ID: <asoM9sKML-7BIEOY@kernel.org> (raw)
In-Reply-To: <20261008140515.GB183998-robh@kernel.org>

On Thu, Oct 08, 2026 at 09:05:15AM -0500, Rob Herring wrote:
> On Thu, Oct 08, 2026 at 11:41:23AM +0200, Marek Szyprowski wrote:
> > Get rid of the static, limited-size reserved_mem array and replace it
> > with array allocated by memblock_alloc_raw() and accessed through a
> > temporary early_memremap() mapping. Such mapping is needed for some
> > architectures (like ARM64), where linear map is not yet available during
> > early boot scan. Having a single, writeable array with all reserved
> > regions removes the need to perform two step initialization introduced
> > by commit 8a6e02d0c00e ("of: reserved_mem: Restructure how the reserved
> > memory regions are processed"), so all regions can be processed
> > directly during the early scan again.
> > 
> > Suggested-by: Mike Rapoport <rppt@kernel.org>
> > Link: https://lore.kernel.org/all/asc6brs_g0ky0wOM@kernel.org/
> > Assisted-By: Claude Opus 5.5 <noreply@anthropic.com>
> 
> Assisted-by: LLM
> 
> is the new way...

Probably not any more :)

https://lore.kernel.org/all/20261009083137.3-1-sashal@kernel.org/
 
> > Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> > ---
> >  drivers/of/fdt.c             |   3 -
> >  drivers/of/of_private.h      |   2 -
> >  drivers/of/of_reserved_mem.c | 251 ++++++++++++++---------------------
> >  3 files changed, 96 insertions(+), 160 deletions(-)

-- 
Sincerely yours,
Mike.

      parent reply	other threads:[~2026-10-10 10:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20261008094129eucas1p2c89032b43a7491f200a703da1a224c2c@eucas1p2.samsung.com>
2026-10-08  9:41 ` [PATCH 0/2] of: reserved_mem: use dynamically allocated reserved_mem array Marek Szyprowski
2026-10-08  9:41   ` [PATCH 1/2] of: reserved_mem: group allocation helpers together Marek Szyprowski
2026-10-08  9:41   ` [PATCH 2/2] of: reserved_mem: allocate and map the reserved_mem array early Marek Szyprowski
2026-10-08  9:59     ` sashiko-bot
2026-10-08 14:05     ` Rob Herring
2026-10-08 15:10       ` Marek Szyprowski
2026-10-10 10:01       ` 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=asoM9sKML-7BIEOY@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=chenwandun1@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=m.szyprowski@samsung.com \
    --cc=quic_obabatun@quicinc.com \
    --cc=robh@kernel.org \
    --cc=saravanak@kernel.org \
    /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