From: Alison Schofield <alison.schofield@intel.com>
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>,
<akpm@linux-foundation.org>, <rrichter@amd.com>,
<bfaccini@nvidia.com>, <haibo1.xu@intel.com>, <david@redhat.com>,
<linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>, <chenbaozi@phytium.com.cn>
Subject: Re: [PATCH v2] mm: numa_memblks: introduce numa_add_reserved_memblk
Date: Thu, 3 Apr 2025 11:37:03 -0700 [thread overview]
Message-ID: <Z-7VT0KQFMQLBnZT@aschofie-mobl2.lan> (raw)
In-Reply-To: <20250328092132.2695299-1-wangyuquan1236@phytium.com.cn>
On Fri, Mar 28, 2025 at 05:21:32PM +0800, Yuquan Wang wrote:
Commit message from v1 needs updating to reflect what this v2
is doing: 'add empty CFMWS ranges to numa_reserved_meminfo"
> With numa_add_reserved_memblk(), kernel could add numa_memblk into
> numa_reserved_meminfo directly.
above comes last in commit log.
ie. State the issue like this:
>
> 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 suppot of future hotplug / CXL provisioning.
'support'
>
Then the resolution:
Introduce and use numa_add_reserved_memblk() to add the empty CFMWS
ranges directly.
> Signed-off-by: Yuquan Wang <wangyuquan1236@phytium.com.cn>
With the above commit message and log updates, and +linux-cxl mail list,
add:
Reviewed-by: Alison Schofield <alison.schofield@intel.com>
> ---
snip
next prev parent reply other threads:[~2025-04-03 18:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2025-04-04 6:29 ` Anshuman Khandual
2025-04-09 4:01 Yuquan Wang
2025-04-09 9:43 ` Mike Rapoport
2025-05-06 6:22 Yuquan Wang
2025-05-07 1:55 ` Andrew Morton
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
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=Z-7VT0KQFMQLBnZT@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=bfaccini@nvidia.com \
--cc=chenbaozi@phytium.com.cn \
--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-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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