From: Gregory Price <gourry@gourry.net>
To: Jonathan Cameron <jonathan.cameron@huawei.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Cui Chao <cuichao1753@phytium.com.cn>,
dan.j.williams@intel.com, Mike Rapoport <rppt@kernel.org>,
Wang Yinfeng <wangyinfeng@phytium.com.cn>,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 1/1] mm: numa_memblks: Identify the accurate NUMA ID of CFMW
Date: Fri, 6 Feb 2026 08:31:09 -0500 [thread overview]
Message-ID: <aYXtHa4Y2y_5xgcS@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <20260206110305.00001fbb@huawei.com>
On Fri, Feb 06, 2026 at 11:03:05AM +0000, Jonathan Cameron wrote:
> On Thu, 5 Feb 2026 18:10:55 -0500
> Gregory Price <gourry@gourry.net> wrote:
>
> I disagree. There is nothing in the specification to say it should do that and
> we have very intentionally not done so in QEMU - this is far from the first
> time this has come up!. We won't be doing so any time soon unless someone
> convinces me with clear spec references and tight reasoning for why it is the
> right thing to do.
>
Interestingly I've had this exact conversation - in reverse - with other
platform folks, who think CFMWS w/o SRAT is broken. It was a zealous
enough opinion that I may have over-indexed on it (plus i've read the
numa mapping code and making this more dynamic seems difficult).
> This configuration reflects the pre hotplug / early CXL deployment
> situation. Now we have proper support in Linux we have moved beyond that.
> We do need to solve the dynamic NUMA node cases though and I'm hoping your
> current work will make that a bit easier.
If we want flexibility to ship HPAs around to different nodes at
runtime, that might cause issues. The page-to-nid / pa-to-nid mapping
code is somewhat expected to be immutable after __init, so there could
be nasty assumptions sprinkled all over the kernel.
That will take some time.
---
Andrew if Jonathan is good with it then with changelog updates this can
go in, otherwise I don't think this warrants a backport or anything.
~Gregory
next prev parent reply other threads:[~2026-02-06 13:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-06 3:10 [PATCH v2 0/1] " Cui Chao
2026-01-06 3:10 ` [PATCH v2 1/1] mm: numa_memblks: " Cui Chao
2026-01-08 16:19 ` Jonathan Cameron
2026-01-08 17:48 ` Andrew Morton
2026-01-15 9:43 ` Cui Chao
2026-01-15 18:18 ` Andrew Morton
2026-01-15 19:50 ` dan.j.williams
2026-01-22 8:03 ` Cui Chao
2026-01-22 21:28 ` Andrew Morton
2026-01-23 8:59 ` Cui Chao
2026-01-23 16:46 ` Gregory Price
2026-01-26 9:06 ` Cui Chao
2026-02-05 22:58 ` Andrew Morton
2026-02-05 23:10 ` Gregory Price
2026-02-06 11:03 ` Jonathan Cameron
2026-02-06 13:31 ` Gregory Price [this message]
2026-02-06 15:09 ` Jonathan Cameron
2026-02-06 15:53 ` Gregory Price
2026-02-06 16:26 ` Jonathan Cameron
2026-02-06 16:32 ` Gregory Price
2026-02-19 14:19 ` Jonathan Cameron
2026-02-06 15:57 ` Andrew Morton
2026-02-06 16:23 ` Jonathan Cameron
2026-01-09 9:35 ` Pratyush Brahma
2026-01-15 10:06 ` Cui Chao
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=aYXtHa4Y2y_5xgcS@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=akpm@linux-foundation.org \
--cc=cuichao1753@phytium.com.cn \
--cc=dan.j.williams@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=qemu-devel@nongnu.org \
--cc=rppt@kernel.org \
--cc=wangyinfeng@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