From: Alison Schofield <alison.schofield@intel.com>
To: Gregory Price <gourry@gourry.net>
Cc: <dan.j.williams@intel.com>, Davidlohr Bueso <dave@stgolabs.net>,
"Jonathan Cameron" <jonathan.cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>, <linux-cxl@vger.kernel.org>
Subject: Re: [PATCH 2/2] cxl/region: Unregister auto-created region when assembly fails
Date: Wed, 4 Feb 2026 16:32:39 -0800 [thread overview]
Message-ID: <aYPlJ2PRv-FaFKFT@aschofie-mobl2.lan> (raw)
In-Reply-To: <aX4kd-S3PQTTWfol@gourry-fedora-PF4VCD3F>
On Sat, Jan 31, 2026 at 10:49:11AM -0500, Gregory Price wrote:
> On Fri, Jan 30, 2026 at 05:04:48PM -0800, Alison Schofield wrote:
> >
> ... snip ...
> Logging in on a saturday, will respond fully on monday just wanted to
> inject a question for the masses here
>
> > When auto-created region assembly fails,
>
> I wonder how many work we want to do to try to make the auto-region
> path more reliable for complex setups (interleaving being one example).
>
> In other paths, in particular when there is some implied use-case for
> the device, we already take the opinion the BIOS should do nothing.
> Should we draw a hard line on when that should be the official opinion?
>
> i.e. auto-decoders should be intended for trivial SysRAM regions only
It has not been my impression that we have that much control over what
BIOS may present. ie. If it is CXL Spec legal they may build it. I
recall you wrote a doc of Linux Expectations of BIOS. Did you actually
try to limit what BIOS does?
>
> (especially given that a user can't even select zone-isolation except
> via a global kernel build option that affects all hotplug memory)
>
> ~Gregory
next prev parent reply other threads:[~2026-02-05 0:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 4:23 [PATCH 1/2] cxl/region: Timeout auto region assembly waiting for endpoints Alison Schofield
2026-01-30 4:23 ` [PATCH 2/2] cxl/region: Unregister auto-created region when assembly fails Alison Schofield
2026-01-30 17:45 ` dan.j.williams
2026-01-31 1:04 ` Alison Schofield
2026-01-31 15:49 ` Gregory Price
2026-02-05 0:32 ` Alison Schofield [this message]
2026-02-05 4:22 ` Gregory Price
2026-02-03 3:07 ` dan.j.williams
2026-02-05 0:20 ` Alison Schofield
2026-02-05 1:03 ` dan.j.williams
2026-01-30 4:58 ` [PATCH 1/2] cxl/region: Timeout auto region assembly waiting for endpoints dan.j.williams
2026-01-30 17:42 ` Gregory Price
2026-01-30 18:26 ` dan.j.williams
2026-01-30 19:03 ` Gregory Price
2026-01-30 22:46 ` dan.j.williams
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=aYPlJ2PRv-FaFKFT@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=gourry@gourry.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--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