From: Xi Ruoyao <xry111@xry111.site>
To: Guenter Roeck <linux@roeck-us.net>,
Yuquan Wang <wangyuquan1236@phytium.com.cn>
Cc: Jonathan.Cameron@huawei.com, dan.j.williams@intel.com,
rppt@kernel.org, rafael@kernel.org, lenb@kernel.org,
akpm@linux-foundation.org, alison.schofield@intel.com,
rrichter@amd.com, bfaccini@nvidia.com, haibo1.xu@intel.com,
david@redhat.com, chenhuacai@kernel.org,
linux-cxl@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
chenbaozi@phytium.com.cn, loongarch@lists.linux.dev
Subject: Re: [PATCH v3 1/1] mm: numa_memblks: introduce numa_add_reserved_memblk
Date: Tue, 03 Jun 2025 21:30:25 +0800 [thread overview]
Message-ID: <4c2f44c4115eae6b68846da1ec85c5f47ea66122.camel@xry111.site> (raw)
In-Reply-To: <06a0abfd-5508-4fb5-8a96-a13cf3d8aca7@roeck-us.net>
On Tue, 2025-06-03 at 06:06 -0700, Guenter Roeck wrote:
> Hi,
>
> On Thu, May 08, 2025 at 10:27:19AM +0800, Yuquan Wang wrote:
> > acpi_parse_cfmws() currently adds empty CFMWS ranges to numa_meminfo
> > with the expectation that numa_cleanup_meminfo moves them to
> > numa_reserved_meminfo. There is no need for that indirection when it
> > is
> > known in advance that these unpopulated ranges are meant for
> > numa_reserved_meminfo in support of future hotplug / CXL
> > provisioning.
> >
> > Introduce and use numa_add_reserved_memblk() to add the empty CFMWS
> > ranges directly.
> >
> > Signed-off-by: Yuquan Wang <wangyuquan1236@phytium.com.cn>
>
> Just on case this has not been reported yet:
>
> Building loongarch:defconfig ... failed
> --------------
> Error log:
> drivers/acpi/numa/srat.c: In function 'acpi_parse_cfmws':
> drivers/acpi/numa/srat.c:467:13: error: implicit declaration of
> function 'numa_add_reserved_memblk'
The fix is queued at
https://git.kernel.org/pub/scm/linux/kernel/git/chenhuacai/linux-loongson.git/commit/?h=loongarch-next&id=a24f2fb70cb62180486ad4d74f809ff35ddd1cf9
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
prev parent reply other threads:[~2025-06-03 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 2:27 Yuquan Wang
2025-05-08 4:09 ` Alison Schofield
2025-05-08 9:45 ` Jonathan Cameron
2025-05-09 0:42 ` Andrew Morton
2025-06-03 13:06 ` Guenter Roeck
2025-06-03 13:30 ` Xi Ruoyao [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=4c2f44c4115eae6b68846da1ec85c5f47ea66122.camel@xry111.site \
--to=xry111@xry111.site \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=bfaccini@nvidia.com \
--cc=chenbaozi@phytium.com.cn \
--cc=chenhuacai@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=haibo1.xu@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@roeck-us.net \
--cc=loongarch@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=rppt@kernel.org \
--cc=rrichter@amd.com \
--cc=wangyuquan1236@phytium.com.cn \
/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