linux-kernel - Re: [PATCH v3 1/1] mm: numa_memblks: introduce numa_add_reserved

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250508104541.00007c4f@huawei.com>
Date: Thu, 8 May 2025 10:45:41 +0100
From: Jonathan Cameron <Jonathan.Cameron@...wei.com>
To: Alison Schofield <alison.schofield@...el.com>
CC: Yuquan Wang <wangyuquan1236@...tium.com.cn>, <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>, <chenhuacai@...nel.org>,
	<linux-cxl@...r.kernel.org>, <linux-acpi@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>,
	<chenbaozi@...tium.com.cn>, <loongarch@...ts.linux.dev>
Subject: Re: [PATCH v3 1/1] mm: numa_memblks: introduce
 numa_add_reserved_memblk

On Wed, 7 May 2025 21:09:07 -0700
Alison Schofield <alison.schofield@...el.com> wrote:

> 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@...tium.com.cn>  
> 
> Reviewed-by: Alison Schofield <alison.schofield@...el.com>
> 
> 
> 

Yuquan - I'm guessing this is a misunderstanding of process.
The patch submitter should pick up tags on previous versions.
If any are not picked up in the tag block there should be a clear
explanation of why!

Jonathan