From: Dave Jiang <dave.jiang@intel.com>
To: Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-cxl@vger.kernel.org
Cc: Ard Biesheuvel <ardb@kernel.org>,
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>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Yazen Ghannam <yazen.ghannam@amd.com>,
Terry Bowman <terry.bowman@amd.com>
Subject: Re: [PATCH v5 0/5] acpi/ghes, cper, cxl: Process CXL CPER Protocol errors
Date: Tue, 21 Jan 2025 13:32:42 -0700 [thread overview]
Message-ID: <977859ca-3971-4d03-b514-9bf37bbceff3@intel.com> (raw)
In-Reply-To: <20250114120427.149260-1-Smita.KoralahalliChannabasappa@amd.com>
On 1/14/25 5:04 AM, Smita Koralahalli wrote:
> This patchset adds logging support for CXL CPER endpoint and port protocol
> errors.
Ard,
Do you mind giving an ACK for the series if it looks ok to you? I can pick up the series through the CXL tree with your ACKs. Thanks!
Smita,
Can you please respin a v6 based on top of latest upstream instead of Terry's changes? I think we are ready to pick this up before Terry's series. Thank you.
>
> The first 3 patches update the existing codebase to support CXL CPER
> Protocol error reporting.
>
> The last 2 patches introduce recognizing and reporting CXL CPER Protocol
> errors.
>
> Should be based on top of:
> https://lore.kernel.org/linux-cxl/20250107143852.3692571-1-terry.bowman@amd.com
>
> Link to v4:
> https://lore.kernel.org/linux-cxl/20241217022032.87298-1-Smita.KoralahalliChannabasappa@amd.com
>
> Changes in v4 -> v5:
> [Dave]: Reviewed-by tags.
> [Jonathan]: Remove blank line.
> [Jonathan, Ira]: Change CXL -> "CXL".
> [Ira]: Fix build error for CONFIG_ACPI_APEI_PCIEAER.
>
> Changes in v3 -> v4:
> [Ira]: Use memcpy() for RAS Cap struct.
> [Jonathan]: Commit description edits.
> [Jonathan]: Use separate work registration functions for protocol and
> component errors.
> [Jonathan, Ira]: Replace flags with separate functions for port and
> device errors.
> [Jonathan]: Use goto for register and unregister calls.
>
> Changes in v2 -> v3:
> [Dan]: Define a new workqueue for CXL CPER Protocol errors and avoid
> reusing existing workqueue which handles CXL CPER events.
> [Dan] Update function and struct names.
> [Ira] Don't define common function get_cxl_devstate().
> [Dan] Use switch cases rather than defining array of structures.
> [Dan] Pass the entire cxl_cper_prot_err struct for CXL subsystem.
> [Dan] Use pr_err_ratelimited().
> [Dan] Use AER_ severities directly. Don't define CXL_ severities.
> [Dan] Limit either to Device ID or Agent Info check.
> [Dan] Validate size of RAS field matches expectations.
>
> Changes in v2 -> v1:
> [Jonathan] Refactor code for trace support. Rename get_cxl_dev()
> to get_cxl_devstate().
> [Jonathan] Cleanups for get_cxl_devstate().
> [Alison, Jonathan]: Define array of structures for Device ID and Serial
> number comparison.
> [Dave] p_err -> rec/p_rec.
> [Jonathan] Remove pr_warn.
>
> Smita Koralahalli (5):
> efi/cper, cxl: Prefix protocol error struct and function names with
> cxl_
> efi/cper, cxl: Make definitions and structures global
> efi/cper, cxl: Remove cper_cxl.h
> acpi/ghes, cper: Recognize and cache CXL Protocol errors
> acpi/ghes, cxl/pci: Process CXL CPER Protocol Errors
>
> drivers/acpi/apei/ghes.c | 103 ++++++++++++++++++++++++++++++++
> drivers/cxl/core/pci.c | 62 +++++++++++++++++++
> drivers/cxl/cxlpci.h | 9 +++
> drivers/cxl/pci.c | 59 +++++++++++++++++-
> drivers/firmware/efi/cper.c | 6 +-
> drivers/firmware/efi/cper_cxl.c | 39 +-----------
> drivers/firmware/efi/cper_cxl.h | 66 --------------------
> include/cxl/event.h | 101 +++++++++++++++++++++++++++++++
> include/linux/cper.h | 8 +++
> 9 files changed, 347 insertions(+), 106 deletions(-)
> delete mode 100644 drivers/firmware/efi/cper_cxl.h
>
next prev parent reply other threads:[~2025-01-21 20:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 12:04 [PATCH v5 0/5] acpi/ghes, cper, cxl: Process CXL CPER Protocol errors Smita Koralahalli
2025-01-14 12:04 ` [PATCH v5 1/5] efi/cper, cxl: Prefix protocol error struct and function names with cxl_ Smita Koralahalli
2025-01-14 12:04 ` [PATCH v5 2/5] efi/cper, cxl: Make definitions and structures global Smita Koralahalli
2025-01-14 12:04 ` [PATCH v5 3/5] efi/cper, cxl: Remove cper_cxl.h Smita Koralahalli
2025-01-14 12:04 ` [PATCH v5 4/5] acpi/ghes, cper: Recognize and cache CXL Protocol errors Smita Koralahalli
2025-01-14 15:40 ` Dave Jiang
2025-01-16 14:57 ` Ira Weiny
2025-01-14 12:04 ` [PATCH v5 5/5] acpi/ghes, cxl/pci: Process CXL CPER Protocol Errors Smita Koralahalli
2025-01-14 15:42 ` Dave Jiang
2025-01-15 13:29 ` Jonathan Cameron
2025-01-16 14:55 ` Ira Weiny
2025-01-21 20:32 ` Dave Jiang [this message]
2025-01-22 19:35 ` [PATCH v5 0/5] acpi/ghes, cper, cxl: Process CXL CPER Protocol errors Koralahalli Channabasappa, Smita
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=977859ca-3971-4d03-b514-9bf37bbceff3@intel.com \
--to=dave.jiang@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=alison.schofield@intel.com \
--cc=ardb@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=terry.bowman@amd.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