[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <63531a9dd51b9_4da32946c@dwillia2-xfh.jf.intel.com.notmuch>
Date: Fri, 21 Oct 2022 15:18:05 -0700
From: Dan Williams <dan.j.williams@...el.com>
To: Smita Koralahalli <Smita.KoralahalliChannabasappa@....com>,
<linux-cxl@...r.kernel.org>, <linux-kernel@...r.kernel.org>
CC: Alison Schofield <alison.schofield@...el.com>,
Vishal Verma <vishal.l.verma@...el.com>,
Ira Weiny <ira.weiny@...el.com>,
Ben Widawsky <bwidawsk@...nel.org>,
Dan Williams <dan.j.williams@...el.com>,
"Robert Richter" <rrichter@....com>,
Yazen Ghannam <yazen.ghannam@....com>,
"Terry Bowman" <terry.bowman@....com>,
Smita Koralahalli <Smita.KoralahalliChannabasappa@....com>,
Ard Biesheuvel <ardb@...nel.org>
Subject: RE: [PATCH 0/2] efi/cper, cxl: Decode CXL Protocol Errors CPER
Hi Smita,
Smita Koralahalli wrote:
> This series adds decoding for the CXL Protocol Errors Common Platform
> Error Record.
Be sure to copy Ard Biesheuvel <ardb@...nel.org>, added, on
drivers/firmware/efi/ patches.
Along those lines, drivers/cxl/ developers have an idea of what is
contained in the new CXL protocol error records and why Linux might want
to decode them, others from outside drivers/cxl/ might not. It always
helps to have a small summary of the benefit to end users of the
motivation to apply a patch set.
>
> Smita Koralahalli (2):
> efi/cper, cxl: Decode CXL Protocol Error Section
> efi/cper, cxl: Decode CXL Error Log
>
> drivers/firmware/efi/Makefile | 2 +-
> drivers/firmware/efi/cper.c | 9 +++
> drivers/firmware/efi/cper_cxl.c | 108 ++++++++++++++++++++++++++++++++
> drivers/firmware/efi/cper_cxl.h | 58 +++++++++++++++++
> include/linux/cxl_err.h | 21 +++++++
> 5 files changed, 197 insertions(+), 1 deletion(-)
I notice no updates for the trace events in ghes_do_proc(), is that next
in your queue? That's ok to be a follow-on after v2.
Powered by blists - more mailing lists