From: Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>
To: Fan Ni <nifan.cxl@gmail.com>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-cxl@vger.kernel.org, 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>,
Bowman Terry <terry.bowman@amd.com>
Subject: Re: [PATCH v2 3/4] acpi/ghes, efi/cper: Recognize and process CXL Protocol Errors.
Date: Thu, 3 Oct 2024 12:19:34 -0700 [thread overview]
Message-ID: <57921df3-6b02-583f-c863-f227ca8103d5@amd.com> (raw)
In-Reply-To: <Zvw0SnS40Rf_jWbB@fan>
On 10/1/2024 10:41 AM, Fan Ni wrote:
> On Tue, Oct 01, 2024 at 12:52:33AM +0000, Smita Koralahalli wrote:
>> UEFI v2.10 section N.2.13 defines a CPER record for CXL Protocol errors.
>>
>> Add GHES support to detect CXL CPER Protocol Error Record and Cache Error
>> Severity, Device ID, Device Serial number and CXL RAS capability struct in
>> struct cxl_cper_prot_err. Include this struct as a member of struct
>> cxl_cper_work_data.
>>
>> Signed-off-by: Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>
>> ---
>> v2:
>> Defined array of structures for Device ID and Serial number
>> comparison.
>> p_err -> rec/p_rec.
>> ---
>> drivers/acpi/apei/ghes.c | 10 +++
>> drivers/firmware/efi/cper_cxl.c | 115 ++++++++++++++++++++++++++++++++
>> include/cxl/event.h | 26 ++++++++
>> 3 files changed, 151 insertions(+)
>>
>> diff --git a/drivers/acpi/apei/ghes.c b/drivers/acpi/apei/ghes.c
>> index ada93cfde9ba..9dcf0f78458f 100644
>> --- a/drivers/acpi/apei/ghes.c
>> +++ b/drivers/acpi/apei/ghes.c
>> @@ -717,6 +717,14 @@ static void cxl_cper_post_event(enum cxl_event_type event_type,
>> schedule_work(cxl_cper_work);
>> }
>>
>> +static void cxl_cper_handle_prot_err(struct acpi_hest_generic_data *gdata)
>> +{
>> + struct cxl_cper_work_data wd;
>> +
>> + if (cxl_cper_handle_prot_err_info(gdata, &wd.p_rec))
>> + return;
>> +}
>
> Why we need a if here? It seems the function will return anyway.
>
> Fan
Yeah, it doesn't make sense here without 4/4.
Thanks
Smita
[snip]
next prev parent reply other threads:[~2024-10-03 19:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 0:52 [PATCH v2 0/4] acpi/ghes, cper, cxl: Trace FW-First CXL Protocol Errors Smita Koralahalli
2024-10-01 0:52 ` [PATCH v2 1/4] efi/cper, cxl: Make definitions and structures global Smita Koralahalli
2024-10-02 23:02 ` Dan Williams
2024-10-03 8:51 ` Ard Biesheuvel
2024-10-01 0:52 ` [PATCH v2 2/4] cxl/pci: Define a common function get_cxl_devstate() Smita Koralahalli
2024-10-01 15:06 ` Ira Weiny
2024-10-02 23:04 ` Dan Williams
2024-10-03 18:44 ` Smita Koralahalli
2024-10-01 0:52 ` [PATCH v2 3/4] acpi/ghes, efi/cper: Recognize and process CXL Protocol Errors Smita Koralahalli
2024-10-01 15:47 ` Ira Weiny
2024-10-01 17:41 ` Fan Ni
2024-10-03 19:19 ` Smita Koralahalli [this message]
2024-10-02 23:47 ` Dan Williams
2024-10-03 19:15 ` Smita Koralahalli
2024-10-03 23:21 ` Dan Williams
2024-10-01 0:52 ` [PATCH v2 4/4] acpi/ghes, cxl/pci: Trace FW-First " Smita Koralahalli
2024-10-01 15:52 ` Ira Weiny
2024-10-03 19:31 ` Smita Koralahalli
2024-10-03 0:16 ` Dan Williams
2024-10-03 20:03 ` Smita Koralahalli
-- strict thread matches above, loose matches on Subject: below --
2024-01-09 3:47 [PATCH v2 0/4] acpi/ghes, cper, cxl: " Smita Koralahalli
2024-01-09 3:47 ` [PATCH v2 3/4] acpi/ghes, efi/cper: Recognize and process " Smita Koralahalli
2024-02-15 12:17 ` Jonathan Cameron
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=57921df3-6b02-583f-c863-f227ca8103d5@amd.com \
--to=smita.koralahallichannabasappa@amd.com \
--cc=Jonathan.Cameron@huawei.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=nifan.cxl@gmail.com \
--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