From: Mike Rapoport <rppt@kernel.org>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: George Guo <dongtai.guo@linux.dev>,
pasha.tatashin@soleen.com, pratyush@kernel.org, ardb@kernel.org,
shuah@kernel.org, ilias.apalodimas@linaro.org,
akpm@linux-foundation.org, baoquan.he@linux.dev,
ruirui.yang@linux.dev, guodongtai@kylinos.cn, kernel@xen0n.name,
graf@amazon.com, liukexin@kylinos.cn, loongarch@lists.linux.dev,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-efi@vger.kernel.org
Subject: Re: [PATCH v6 5/8] LoongArch: Allow memblock arrays to resize
Date: Sun, 8 Nov 2026 10:14:46 +0200 [thread overview]
Message-ID: <avAvdiYY7SJ_Gfwt@kernel.org> (raw)
In-Reply-To: <CAAhV-H6aO_QNEzV-r6+FbNa=9EUQgv1vH0ET-ETXAH5x6oQGjA@mail.gmail.com>
On Fri, Nov 06, 2026 at 10:35:01PM +0800, Huacai Chen wrote:
> On Fri, Nov 6, 2026 at 12:07 AM Mike Rapoport <rppt@kernel.org> wrote:
> >
> > On Thu, Nov 05, 2026 at 11:07:01PM +0800, Huacai Chen wrote:
> > > Hi, Mike,
> > >
> > > On Thu, Nov 5, 2026 at 8:57 PM Mike Rapoport <rppt@kernel.org> wrote:
> > > >
> > > > On Fri, Oct 30, 2026 at 02:29:52AM +0900, George Guo wrote:
> > > > > From: George Guo <guodongtai@kylinos.cn>
> > > > >
> > > > > LoongArch never calls memblock_allow_resize(), so the reserved region
> > > > > array cannot grow beyond INIT_MEMBLOCK_RESERVED_REGIONS entries
> > > > > (INIT_MEMBLOCK_REGIONS + NR_CPUS).
> > > >
> > > > This might be something to fix independent of KHO.
> > > >
> > > > Huacai,
> > > >
> > > > What's the reason LoongArch never enables memblock resizing and why it
> > > > defines INIT_MEMBLOCK_RESERVED_REGIONS to include NR_CPUS?
> > > At first we didn't define INIT_MEMBLOCK_RESERVED_REGIONS, then we got
> > > boot failures on a 128-cores machine, so define it, and the value is
> > > similar to arm64.
> >
> > AFAIR, arm64 had to reserve some per cpu data before they could enable
> > memblock resizing, so they had to make it static.
> LoongArch is similar, so below 64-cores machine has no problem.
>
> >
> > > The reason LoongArch never enables memblock resizing is because the mm
> > > code is derived from MIPS, and MIPS never enables it.
> >
> > If that's the only reason, you might want to revisit that :)
> Yes, it seems we need memblock_allow_resize(), but maybe it is better
> to bring back paging_init()? Most other archs call
> memblock_allow_resize() in paging_init().
paging_init() is a historical relict that hugely misnamed everywhere :)
I think platform_init() should be fine.
As far as I can tell, by the time platform_init() calls init_numa_memory(),
all memory reservations that must happen before any memblock allocations
are done.
> Huacai
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-11-08 8:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 17:29 [PATCH v6 0/8] LoongArch: Add KHO support and selftests George Guo
2026-10-29 17:29 ` [PATCH v6 1/8] efi: Pass KHO state to the next kernel in a configuration table George Guo
2026-10-29 19:28 ` Ard Biesheuvel
2026-10-29 19:42 ` Pratyush Yadav
2026-11-03 10:29 ` George Guo
2026-11-04 3:59 ` Huacai Chen
2026-11-04 14:54 ` Mukesh Pilaniya
2026-10-29 17:29 ` [PATCH v6 2/8] kho: Write KHO state to the EFI table at kexec time George Guo
2026-10-29 17:29 ` [PATCH v6 3/8] kho: Include linux/mm.h in kho_block.c George Guo
2026-10-29 17:29 ` [PATCH v6 4/8] kho: Add kho_disable() George Guo
2026-11-05 12:53 ` Mike Rapoport
2026-10-29 17:29 ` [PATCH v6 5/8] LoongArch: Allow memblock arrays to resize George Guo
2026-11-05 12:57 ` Mike Rapoport
2026-11-05 15:07 ` Huacai Chen
2026-11-05 16:07 ` Mike Rapoport
2026-11-06 14:35 ` Huacai Chen
2026-11-08 8:14 ` Mike Rapoport [this message]
2026-11-08 8:26 ` Huacai Chen
2026-10-29 17:29 ` [PATCH v6 6/8] LoongArch: Enable kexec handover (KHO) George Guo
2026-10-29 17:29 ` [PATCH v6 7/8] selftests/kho: Add LoongArch vmtest support George Guo
2026-10-29 17:29 ` [PATCH v6 8/8] selftests/liveupdate: " George Guo
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=avAvdiYY7SJ_Gfwt@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ardb@kernel.org \
--cc=baoquan.he@linux.dev \
--cc=chenhuacai@kernel.org \
--cc=dongtai.guo@linux.dev \
--cc=graf@amazon.com \
--cc=guodongtai@kylinos.cn \
--cc=ilias.apalodimas@linaro.org \
--cc=kernel@xen0n.name \
--cc=kexec@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liukexin@kylinos.cn \
--cc=loongarch@lists.linux.dev \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=ruirui.yang@linux.dev \
--cc=shuah@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
all inboxes | Powered by JetHome®