From: Ira Weiny <ira.weiny@intel.com>
To: Ira Weiny <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>,
Shiju Jose <shiju.jose@huawei.com>
Cc: Yazen Ghannam <yazen.ghannam@amd.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>,
"Ard Biesheuvel" <ardb@kernel.org>, <linux-efi@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-cxl@vger.kernel.org>,
Ira Weiny <ira.weiny@intel.com>
Subject: Re: [PATCH v3 6/7] firmware/efi: Process CXL Component Events
Date: Thu, 14 Dec 2023 10:24:26 -0800 [thread overview]
Message-ID: <657b485a49a06_273ab0294ae@iweiny-mobl.notmuch> (raw)
In-Reply-To: <20231213-cxl-cper-v3-6-7fd863dd0d25@intel.com>
Ira Weiny wrote:
> BIOS can configure memory devices as firmware first. This will send CXL
> events to the firmware instead of the OS. The firmware can then send
> these events to the OS via UEFI.
>
> UEFI v2.10 section N.2.14 defines a Common Platform Error Record (CPER)
> format for CXL Component Events. The format is mostly the same as the
> CXL Common Event Record Format. The difference is the use of a GUID in
> the Section Type rather than a UUID as part of the event itself.
>
> Add EFI support to detect CXL CPER records and call a registered
> notifier with the event. Enforce that only one notifier call can be
> registered at any time.
>
> Cc: Ard Biesheuvel <ardb@kernel.org>
> Signed-off-by: Ira Weiny <ira.weiny@intel.com>
V4 coming with 0day build fixes for the CONFIG_UEFI_CPER=n case.
Ira
next prev parent reply other threads:[~2023-12-14 18:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 1:19 [PATCH v3 0/7] efi/cxl-cper: Report CPER CXL component events through trace events Ira Weiny
2023-12-14 1:19 ` [PATCH v3 1/7] cxl/trace: Pass uuid explicitly to event traces Ira Weiny
2023-12-14 1:19 ` [PATCH v3 2/7] cxl/events: Promote CXL event structures to a core header Ira Weiny
2023-12-14 1:19 ` [PATCH v3 3/7] cxl/events: Create common event UUID defines Ira Weiny
2023-12-14 1:19 ` [PATCH v3 4/7] cxl/events: Separate UUID from event structures Ira Weiny
2023-12-14 1:19 ` [PATCH v3 5/7] cxl/events: Create a CXL event union Ira Weiny
2023-12-14 1:19 ` [PATCH v3 6/7] firmware/efi: Process CXL Component Events Ira Weiny
2023-12-14 18:24 ` Ira Weiny [this message]
2023-12-14 1:20 ` [PATCH v3 7/7] cxl/memdev: Register for and process CPER events Ira Weiny
2023-12-14 15:45 ` [PATCH v3 0/7] efi/cxl-cper: Report CPER CXL component events through trace events Ira Weiny
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=657b485a49a06_273ab0294ae@iweiny-mobl.notmuch \
--to=ira.weiny@intel.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=alison.schofield@intel.com \
--cc=ardb@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shiju.jose@huawei.com \
--cc=vishal.l.verma@intel.com \
--cc=yazen.ghannam@amd.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).