From: Dan Williams <dan.j.williams@intel.com>
To: Alison Schofield <alison.schofield@intel.com>,
"Fabio M. De Francesco" <fabio.m.de.francesco@linux.intel.com>
Cc: 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>,
"Dan Williams" <dan.j.williams@intel.com>,
<linux-cxl@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cxl/acpi: Warn on unsupported platform config detection
Date: Tue, 25 Jun 2024 16:41:22 -0700 [thread overview]
Message-ID: <667b55a2865ab_5639294ef@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <ZnXpPGV57o7v4xYT@aschofie-mobl2>
Alison Schofield wrote:
> On Wed, Jun 19, 2024 at 02:59:41PM +0200, Fabio M. De Francesco wrote:
>
> Hi Fabio,
> You've written such a detailed commit msg, that it pulls me in,
> and now I want to understand more....
>
>
> > Each Host Bridge instance has a corresponding CXL Host Bridge Structure
> > (CHBS) ACPI table that identifies its capabilities. CHBS tables can be
> > two types: RCRB and CHBCR.
>
> Is there a spec reference for this?
> While you're spelling things out, please expand RCRB and CHBCR
>
> >
> > If a Host Bridge is attached to a device that is operating in Restricted
> > CXL Device Mode (RCD), BIOS publishes an RCRB with the base address of
> > registers that describe its capabilities.
> >
> > However, the new (CXL 2.0+) Component registers (e.g., Extended Security
> > Capability), can only be accessed by means of a base address published
> > with a CHBCR.
> >
> > An algorithm to locate a CHBCR associated with an RCRB would be too
> > invasive to land without some concrete motivation.
> >
> > Therefore, just print a message to inform of unsupported config.
> >
>
>
> Were users seeing this and confused by this silent failure?
> What did it look like before?
This is a "by inspection" realization that the CXL specification
currently does not define a mechanism for finding CXL-2.0-only root-port
component regsiters like HDM decoders and Extended Security capability.
Rather than go through a fire drill of clarifying how that is supposed
to work, just the known conflict for now.
When / if someone actually shows up with an eRCD (a device that forces
the host-bridge into CXL 1.1 Restricted CXL Host mode) then we can
consider if Linux needs to do the work to support that. To my knowledge
all of the commercial devices on the market are so-called "CXL 1.1+"
which support training in VH (CXL Virtual Host) mode when attached to a
CXL 2.0 host. So, Linux can likely live with disclaiming "eRCD attached
to a VH host support" for the foreseeable future.
next prev parent reply other threads:[~2024-06-25 23:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 12:59 [PATCH] cxl/acpi: Warn on unsupported platform config detection Fabio M. De Francesco
2024-06-21 20:57 ` Alison Schofield
2024-06-25 23:41 ` Dan Williams [this message]
2024-06-26 10:00 ` Fabio M. De Francesco
2024-06-25 23:14 ` Dan Williams
2024-06-26 10:28 ` Fabio M. De Francesco
2024-06-26 0:10 ` Alison Schofield
2024-06-26 0:45 ` Dan Williams
2024-06-26 10:31 ` Fabio M. De Francesco
2024-06-27 1:09 ` Dan 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=667b55a2865ab_5639294ef@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=fabio.m.de.francesco@linux.intel.com \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.