All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jonathan.cameron@huawei.com>
To: Gregory Price <gourry@gourry.net>
Cc: <linux-cxl@vger.kernel.org>, <linux-doc@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <kernel-team@meta.com>,
	<dave@stgolabs.net>, <dave.jiang@intel.com>,
	<alison.schofield@intel.com>, <vishal.l.verma@intel.com>,
	<ira.weiny@intel.com>, <dan.j.williams@intel.com>,
	<corbet@lwn.net>, <rakuram.e96@gmail.com>, <alucerop@amd.com>
Subject: Re: [PATCH v3 1/2] Documentation/driver-api/cxl: BIOS/EFI expectation update
Date: Fri, 19 Dec 2025 17:28:10 +0000	[thread overview]
Message-ID: <20251219172810.00002e70@huawei.com> (raw)
In-Reply-To: <20251219170538.1675743-2-gourry@gourry.net>

On Fri, 19 Dec 2025 12:05:37 -0500
Gregory Price <gourry@gourry.net> wrote:

> Add a snippet about what Linux expects BIOS/EFI to do (and not
> to do) to the BIOS/EFI section.
> 
> Suggested-by: Alejandro Lucero Palau <alucerop@amd.com>
> Signed-off-by: Gregory Price <gourry@gourry.net>

Nice.  Best of all I can blame you if our bios folk moan at me :)

Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>

> ---
>  .../driver-api/cxl/platform/bios-and-efi.rst  | 20 +++++++++++++++++++
>  1 file changed, 20 insertions(+)
> 
> diff --git a/Documentation/driver-api/cxl/platform/bios-and-efi.rst b/Documentation/driver-api/cxl/platform/bios-and-efi.rst
> index a9aa0ccd92af..9034c206cf8e 100644
> --- a/Documentation/driver-api/cxl/platform/bios-and-efi.rst
> +++ b/Documentation/driver-api/cxl/platform/bios-and-efi.rst
> @@ -29,6 +29,26 @@ at :doc:`ACPI Tables <acpi>`.
>     on physical memory region size and alignment, memory holes, HDM interleave,
>     and what linux expects of HDM decoders trying to work with these features.
>  
> +
> +Linux Expectations of BIOS/EFI Software
> +=======================================
> +Linux expects BIOS/EFI software to construct sufficient ACPI tables (such as
> +CEDT, SRAT, HMAT, etc) and platform-specific configurations (such as HPA spaces
> +and host-bridge interleave configurations) to allow the Linux driver to
> +subsequently configure the devices in the CXL fabric at runtime.
> +
> +Programming of HDM decoders and switch ports is not required, and may be
> +deferred to the CXL driver based on admin policy (e.g. udev rules).
> +
> +Some platforms may require pre-programming HDM decoders and locking them
> +due to quirks (see: Zen5 address translation), but this is not the normal,
> +"expected" configuration path.  This should be avoided if possible.
> +
> +Some platforms may wish to pre-configure these resources to bring memory
> +up without requiring CXL driver support.  These platform vendors should
> +test their configurations with the existing CXL driver and provide driver
> +support for their auto-configurations if features like RAS are required.
> +
>  UEFI Settings
>  =============
>  If your platform supports it, the :code:`uefisettings` command can be used to


  reply	other threads:[~2025-12-19 17:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19 17:05 [PATCH v3 0/2] Documentation/driver-api/cxl: device hotplug Gregory Price
2025-12-19 17:05 ` [PATCH v3 1/2] Documentation/driver-api/cxl: BIOS/EFI expectation update Gregory Price
2025-12-19 17:28   ` Jonathan Cameron [this message]
2025-12-19 17:49     ` Gregory Price
2025-12-20  6:53   ` Alejandro Lucero Palau
2026-01-05 21:00   ` Dave Jiang
2025-12-19 17:05 ` [PATCH v3 2/2] Documentation/driver-api/cxl: device hotplug section Gregory Price
2025-12-20  6:56   ` Alejandro Lucero Palau
2026-01-05 21:10   ` Dave Jiang
2026-01-07  2:19   ` Alison Schofield
2026-01-07 15:54     ` Gregory Price
2026-01-08  5:42       ` Alison Schofield
2026-01-06 17:54 ` [PATCH v3 0/2] Documentation/driver-api/cxl: device hotplug Dave Jiang

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=20251219172810.00002e70@huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=alison.schofield@intel.com \
    --cc=alucerop@amd.com \
    --cc=corbet@lwn.net \
    --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=kernel-team@meta.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rakuram.e96@gmail.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 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.