From: Gregory Price <gourry@gourry.net>
To: "Huang, Kai" <kai.huang@intel.com>
Cc: "Schofield, Alison" <alison.schofield@intel.com>,
"nunodasneves@linux.microsoft.com"
<nunodasneves@linux.microsoft.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"rafael@kernel.org" <rafael@kernel.org>,
"thorsten.blum@linux.dev" <thorsten.blum@linux.dev>,
"wangyuquan1236@phytium.com.cn" <wangyuquan1236@phytium.com.cn>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"lenb@kernel.org" <lenb@kernel.org>,
"xueshuai@linux.alibaba.com" <xueshuai@linux.alibaba.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] ACPI: NUMA: Only parse CFMWS at boot when CXL_ACPI is on
Date: Wed, 4 Mar 2026 19:29:38 -0500 [thread overview]
Message-ID: <aajOckpcmQwYydVQ@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <4809035f61dcd6ace773532efe46b0f1928be313.camel@intel.com>
On Thu, Mar 05, 2026 at 12:14:52AM +0000, Huang, Kai wrote:
> On Wed, 2026-03-04 at 18:56 -0500, Gregory Price wrote:
> >
> > This basically says if specifically CXL_ACPI is built out, the NUMA
> > structure is forever lost - even though it's accurately described by
> > BIOS.
> >
>
> The normal NUMA info described in SRAT is still there. It only avoids
> detecting CFMWS, which doesn't provide any NUMA info actually -- that's why
> kernel assigns a 'faked' NUMA node for each of them.
>
> So we are not losing anything AFAICT.
Well, I'm mostly confused why there are CEDT entries for hardware that
presumably isn't even there - unless this platform is reserving space
for future hotplug. Just want to make sure we're not adjusting for
strange firmware behavior.
The only platform we've seen this behavior on previously was QEMU, but
that was because it never emitted SRAT, so i was wondering if there's
odd firmware behavior going on (emitting CEDTs when it shouldn't) before
we jump to dropping nodes that would have otherwise have been present
on existing systems who might have compiled CXL_ACPI out.
You are taking something away by nature of compiling something out by
default that was previously not compiled out by default.
~Gregory
next prev parent reply other threads:[~2026-03-05 0:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 21:33 [PATCH] ACPI: NUMA: Only parse CFMWS at boot when CXL_ACPI is on Kai Huang
2026-03-04 22:33 ` Gregory Price
2026-03-04 23:20 ` Alison Schofield
2026-03-04 23:56 ` Gregory Price
2026-03-05 0:14 ` Huang, Kai
2026-03-05 0:29 ` Gregory Price [this message]
2026-03-05 0:45 ` Huang, Kai
2026-03-05 1:05 ` Gregory Price
2026-03-05 1:29 ` dan.j.williams
2026-03-05 1:51 ` Huang, Kai
2026-03-05 2:08 ` dan.j.williams
2026-03-05 2:22 ` Gregory Price
2026-03-05 3:01 ` dan.j.williams
2026-03-05 10:24 ` Huang, Kai
2026-03-05 8:11 ` Haifeng Xu
2026-03-05 10:25 ` Huang, Kai
2026-03-05 11:26 ` Haifeng Xu
2026-03-05 0:04 ` Huang, Kai
2026-03-05 0:44 ` Alison Schofield
2026-03-05 1:12 ` Huang, Kai
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=aajOckpcmQwYydVQ@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=kai.huang@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=nunodasneves@linux.microsoft.com \
--cc=rafael@kernel.org \
--cc=thorsten.blum@linux.dev \
--cc=wangyuquan1236@phytium.com.cn \
--cc=xueshuai@linux.alibaba.com \
/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