[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Z-7VT0KQFMQLBnZT@aschofie-mobl2.lan>
Date: Thu, 3 Apr 2025 11:37:03 -0700
From: Alison Schofield <alison.schofield@...el.com>
To: Yuquan Wang <wangyuquan1236@...tium.com.cn>
CC: <Jonathan.Cameron@...wei.com>, <dan.j.williams@...el.com>,
<rppt@...nel.org>, <rafael@...nel.org>, <lenb@...nel.org>,
<akpm@...ux-foundation.org>, <rrichter@....com>, <bfaccini@...dia.com>,
<haibo1.xu@...el.com>, <david@...hat.com>, <linux-acpi@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>,
<chenbaozi@...tium.com.cn>
Subject: Re: [PATCH v2] mm: numa_memblks: introduce numa_add_reserved_memblk
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@...tium.com.cn>
With the above commit message and log updates, and +linux-cxl mail list,
add:
Reviewed-by: Alison Schofield <alison.schofield@...el.com>
> ---
snip
Powered by blists - more mailing lists