From: Davidlohr Bueso <dave@stgolabs.net>
To: "Fabio M. De Francesco" <fabio.m.de.francesco@linux.intel.com>
Cc: Jonathan Cameron <jonathan.cameron@huawei.com>,
Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
linux-kernel@vger.kernel.org, linux-cxl@vger.kernel.org
Subject: Re: [PATCH v2] cxl/acpi: Warn on mixed CXL VH and RCH/RCD Hierarchy
Date: Mon, 1 Jul 2024 08:49:32 -0700 [thread overview]
Message-ID: <20240701154932.ch7b75m5xp62oly7@offworld> (raw)
In-Reply-To: <20240628175535.272472-1-fabio.m.de.francesco@linux.intel.com>
On Fri, 28 Jun 2024, Fabio M. De Francesco wrote:
>Each Host Bridge instance has a corresponding CXL Host Bridge Structure
>(CHBS) ACPI table that identifies its capabilities. CHBS tables can be
>two types (CXL 3.1 Table 9-21): The PCIe Root Complex Register Block
>(RCRB) and CXL Host Bridge Component Registers (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 (CXL 3.1 sec. 9.11).
>
>Instead, the new (CXL 2.0+) Component registers can only be accessed
>by means of a base address published with a CHBCR (CXL 3.1 sec. 9.12).
>
>If an eRCD (a device that forces the host-bridge into CXL 1.1 Restricted
>CXL Host mode) is attached to a CXL 2.0+ Host-Bridge, the current CXL
>specification does not define a mechanism for finding CXL-2.0-only
>root-port component registers like HDM decoders and Extended Security
>capability.
>
>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.
>
>Count how many different CHBS "Version" types are detected by
>cxl_get_chbs_iter(). Then make cxl_get_chbs() print a warning if that sum
>is greater than 1.
>
>Tested-by: Alison Schofield <alison.schofield@intel.com>
>Signed-off-by: Fabio M. De Francesco <fabio.m.de.francesco@linux.intel.com>
Reviewed-by: Davidlohr Bueso <dave@stgolabs.net>
next prev parent reply other threads:[~2024-07-01 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 17:48 [PATCH v2] cxl/acpi: Warn on mixed CXL VH and RCH/RCD Hierarchy Fabio M. De Francesco
2024-07-01 15:49 ` Davidlohr Bueso [this message]
2024-07-01 22:17 ` Alison Schofield
2024-07-02 19:14 ` Fabio M. De Francesco
2024-07-02 22:59 ` Alison Schofield
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=20240701154932.ch7b75m5xp62oly7@offworld \
--to=dave@stgolabs.net \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox