From: "Jiaxun Yang" <jiaxun.yang@flygoat.com>
To: "David Woodhouse" <dwmw2@infradead.org>,
"Bernardo C. Gutierrez Cantu" <bercantu@amazon.de>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
"kernel test robot" <lkp@intel.com>,
rppt@kernel.org, yajun.deng@linux.dev,
"Huang Pei" <huangpei@loongson.cn>,
"Thomas Bogendoerfer" <tsbogend@alpha.franken.de>,
"Huacai Chen" <chenhuacai@kernel.org>,
"linux-mips@vger.kernel.org" <linux-mips@vger.kernel.org>
Subject: Re: [PATCH] mm: memblock: Fix arguments passed to memblock_set_node()
Date: Fri, 25 Apr 2025 15:37:37 +0100 [thread overview]
Message-ID: <1d6c1572-25fd-4865-9a61-d58d58d163f1@app.fastmail.com> (raw)
In-Reply-To: <16911666479b2fe4bc65944605199a8b3f12e875.camel@infradead.org>
在2025年4月25日周五 下午3:18,David Woodhouse写道:
[...]
Hi David & co,
>
>
> I did a quick grep for memblock_set_node() callers, and the one in
> szmem() in arch/mips/loongson64/init.c looks odd.
>
> /* set nid for reserved memory */
> memblock_set_node((u64)node << 44, (u64)(node + 1) << 44,
> &memblock.reserved, node);
>
> At first glance I suspect the 'size' should just be (1<<44) or maybe it
> should be inside the loop over the memmap, and called with mem_start,
> mem_size each time?
You are right, it should be (1 << 44), it is an oversight when I was
converting MIPS private boot allocator to memblock.
>
> And why are we calling memblock_reserve() for what appears to be a
> single system-wide vgabios_addr, repeatedly each time szmem() is called
> for a different NUMA node?
Alas this should be done only for node 0.
Thanks
>
>
> 附件:
> * smime.p7s
--
- Jiaxun
next prev parent reply other threads:[~2025-04-25 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 10:02 [PATCH v4] mm: pass nid to reserve_bootmem_region() Gutierrez Cantu, Bernardo
2025-04-25 10:20 ` [PATCH] mm: memblock: Fix arguments passed to memblock_set_node() Bernardo C. Gutierrez Cantu
2025-04-25 14:18 ` David Woodhouse
2025-04-25 14:37 ` Jiaxun Yang [this message]
2025-04-26 1:05 ` Andrew Morton
2025-04-28 9:13 ` Bernardo C. Gutierrez Cantu
2025-04-26 8:22 ` Mike Rapoport
2025-04-28 9:53 ` Bernardo C. Gutierrez Cantu
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=1d6c1572-25fd-4865-9a61-d58d58d163f1@app.fastmail.com \
--to=jiaxun.yang@flygoat.com \
--cc=akpm@linux-foundation.org \
--cc=bercantu@amazon.de \
--cc=chenhuacai@kernel.org \
--cc=dwmw2@infradead.org \
--cc=huangpei@loongson.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=rppt@kernel.org \
--cc=tsbogend@alpha.franken.de \
--cc=yajun.deng@linux.dev \
/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