From: Andrew Morton <akpm@linux-foundation.org>
To: 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,
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 v2] mm: numa_memblks: introduce numa_add_reserved_memblk
Date: Tue, 6 May 2025 18:55:44 -0700 [thread overview]
Message-ID: <20250506185544.474d025e43ebadadaedb982a@linux-foundation.org> (raw)
In-Reply-To: <20250506062245.3816791-1-wangyuquan1236@phytium.com.cn>
On Tue, 6 May 2025 14:22:45 +0800 Yuquan Wang <wangyuquan1236@phytium.com.cn> 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>
> ---
>
> Changes in v2 (Thanks to Dan & Alison):
> - Use numa_add_reserved_memblk() to replace numa_add_memblk() in acpi_parse_cfmws()
> - Add comments to describe the usage of numa_add_reserved_memblk()
> - Updating the commit message to clarify the purpose of the patch
>
> By the way, "LoongArch: Introduce the numa_memblks conversion" is in linux-next.
So is this patch dependent upon "LoongArch: Introduce the numa_memblks
conversion"?
next prev parent reply other threads:[~2025-05-07 1:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 6:22 Yuquan Wang
2025-05-07 1:55 ` Andrew Morton [this message]
2025-05-07 15:21 ` Mike Rapoport
2025-05-07 15:20 ` Mike Rapoport
2025-05-07 16:24 ` Jonathan Cameron
2025-05-08 1:47 ` Yuquan Wang
2025-05-08 1:54 ` Huacai Chen
-- strict thread matches above, loose matches on Subject: below --
2025-04-09 4:01 Yuquan Wang
2025-04-09 9:43 ` Mike Rapoport
2025-03-28 9:21 Yuquan Wang
2025-03-28 13:15 ` kernel test robot
2025-04-03 21:01 ` Dan Williams
2025-04-09 4:08 ` Yuquan Wang
2025-04-09 4:14 ` Dan Williams
2025-03-28 22:53 ` Mike Rapoport
2025-04-03 12:16 ` Jonathan Cameron
2025-04-03 18:37 ` Alison Schofield
2025-04-04 6:29 ` Anshuman Khandual
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=20250506185544.474d025e43ebadadaedb982a@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Jonathan.Cameron@huawei.com \
--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=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