From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: Yuquan Wang <wangyuquan1236@phytium.com.cn>,
<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>,
<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: Thu, 8 May 2025 10:45:41 +0100 [thread overview]
Message-ID: <20250508104541.00007c4f@huawei.com> (raw)
In-Reply-To: <aBwuY7Rj3mpr5Pm4@aschofie-mobl2.lan>
On Wed, 7 May 2025 21:09:07 -0700
Alison Schofield <alison.schofield@intel.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@phytium.com.cn>
>
> Reviewed-by: Alison Schofield <alison.schofield@intel.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
next prev parent reply other threads:[~2025-05-08 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-08 2:27 [PATCH v3 1/1] mm: numa_memblks: introduce numa_add_reserved_memblk Yuquan Wang
2025-05-08 4:09 ` Alison Schofield
2025-05-08 9:45 ` Jonathan Cameron [this message]
2025-05-09 0:42 ` Andrew Morton
2025-06-03 13:06 ` Guenter Roeck
2025-06-03 13:30 ` Xi Ruoyao
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=20250508104541.00007c4f@huawei.com \
--to=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=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