From: Gregory Price <gourry@gourry.net>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Guixin Liu <kanie@linux.alibaba.com>,
Davidlohr Bueso <dave@stgolabs.net>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Dan Williams <djbw@kernel.org>, Ira Weiny <iweiny@kernel.org>,
Li Ming <ming.li@zohomail.com>,
linux-cxl@vger.kernel.org
Subject: Re: [PATCH] cxl/region: Create node access attributes for CFMWS-only NUMA nodes
Date: Thu, 17 Sep 2026 19:33:39 -0400 [thread overview]
Message-ID: <aqx4gd_VO_KhQ9bD@gourry-fedora-PF4VCD3F> (raw)
In-Reply-To: <20260917220432.44c703a1@jic23-hlaptop>
On Thu, Sep 17, 2026 at 10:04:32PM +0100, Jonathan Cameron wrote:
> On Wed, 16 Sep 2026 13:59:48 -0400
> Gregory Price <gourry@gourry.net> wrote:
>
> > On Wed, Sep 16, 2026 at 08:03:38PM +0800, Guixin Liu wrote:
> > > Tested on a QEMU CXL topology with a CFMWS window whose memory is not
> > > described by SRAT or HMAT
> >
> > Sigh. This keeps coming up. (Not your issue Guixin Liu)
>
> I won't reply in depth again. If a platform supports non trivial hotplug
> (i.e. more than one device spec) then the bios has to be clairvoyant
> to create those tables in a fashion that is useful. Generic Ports were
> added to put the missing piece in to solve the problem so there
> is no longer a need to pre bake.
>
Well sure, but [SRAT, Generic Ports] - pick one.
But giving nothing is just a wart :|
> This is going to be more fun when we have more complex devices showing
> up and need to create a NUMA node per device (i.e. those nice compression
> devices of yours). At that point you aren't using SRAT memory proximity
> nodes anyway - unless they are all there at boot and you are spinning a PXM
> for each one. How do you do if a mix of different sized (or at least
> sizes you didn't know at boot) devices get hotplugged later?
cough
https://lore.kernel.org/linux-mm/20260610014517.253609-1-gourry@gourry.net/
next prev parent reply other threads:[~2026-09-17 23:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 12:03 [PATCH] cxl/region: Create node access attributes for CFMWS-only NUMA nodes Guixin Liu
2026-09-16 12:15 ` sashiko-bot
2026-09-16 17:49 ` Dave Jiang
2026-09-17 2:00 ` Guixin Liu
2026-09-16 17:59 ` Gregory Price
2026-09-17 21:04 ` Jonathan Cameron
2026-09-17 23:33 ` Gregory Price [this message]
2026-09-16 18:00 ` Jonathan Cameron
2026-09-17 2:03 ` Guixin Liu
2026-09-16 20:56 ` Alison Schofield
2026-09-17 2:04 ` Guixin Liu
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=aqx4gd_VO_KhQ9bD@gourry-fedora-PF4VCD3F \
--to=gourry@gourry.net \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=djbw@kernel.org \
--cc=iweiny@kernel.org \
--cc=jic23@kernel.org \
--cc=kanie@linux.alibaba.com \
--cc=linux-cxl@vger.kernel.org \
--cc=ming.li@zohomail.com \
--cc=vishal.l.verma@intel.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