From: Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>
To: Ira Weiny <ira.weiny@intel.com>,
linux-efi@vger.kernel.org, linux-cxl@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: Ard Biesheuvel <ardb@kernel.org>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Yazen Ghannam <yazen.ghannam@amd.com>
Subject: Re: [PATCH 1/3] efi/cper, cxl: Decode CXL Component Events General Media Event Record
Date: Tue, 17 Oct 2023 13:52:05 -0700 [thread overview]
Message-ID: <d5882c60-6636-f651-2886-02c433f77ae1@amd.com> (raw)
In-Reply-To: <65288e68de994_2347eb294c2@iweiny-mobl.notmuch>
Hi Ira,
On 10/12/2023 5:25 PM, Ira Weiny wrote:
> Smita Koralahalli wrote:
>> Add support for decoding CXL Component Events General Media Event Record
>> as defined in CXL rev 3.0 section 8.2.9.2.1.1.
>>
>> All the event records as defined in Event Record Identifier field of the
>> Common Event Record Format in CXL rev 3.0 section 8.2.9.2.1 follow the
>> CPER format for representing the hardware errors if reported by a
>> platform.
>>
>> According to the CPER format, each event record including the General
>> Media is logged as a CXL Component Event as defined in UEFI 2.10
>> Section N.2.14 and is identified by a UUID as defined by Event Record
>> Identifier field in Common Event Record Format of CXL rev 3.0 section
>> 8.2.9.2.1. CXL Component Event Log field in Component Events Section
>> corresponds to the component/event specified by the section type UUID.
>>
>> Add support for decoding CXL Component Events as defined in UEFI 2.10
>> Section N.2.14 and decoding Common Event Record as defined in CXL rev 3.0
>> section 8.2.9.2.1.
>>
>> Signed-off-by: Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>
>
> [snip]
>
>> +
>> +/*
>> + * Compute Express Link Common Event Record
>> + * CXL rev 3.0 section 8.2.9.2.1; Table 8-42
>> + */
>> +struct common_event_record {
>> + u8 identifier[16];
>
> I interpreted the CPER structure as not having this identifier here.
>
> From Section N.2.14:
>
> "For the CXL Component Event Log: Refer to the Common Event Record field
> (Offset 16) of the Events Record Format for each CXL component."
>
> This implies that the data coming from the CPER record starts at length.
Thanks for pointing this out. According to Spec, you are right. Our
records did show up the identifier. Hence, I added that field. We should
probably fix it from our end.
Meanwhile, I'm taking a look at your patches.
Thanks,
Smita
>
> I'd be happy if my interpretation is wrong. But if I am wrong then there
> is no reason to duplicate these structures which are already defined in
> cxlmem.h
>
> I was plumbing up the cxl code to make a copy from length on and splice in
> the uuid from the guid passed from the Section Type.
>
> Ira
>
>> + u8 length;
>> + u8 flags[3];
>> + u16 handle;
>> + u16 related_handle;
>> + u64 timestamp;
>> + u8 maint_op_class;
>> + u8 reserved[15];
>> +};
>> +
>> +/*
>> + * CXL General Media Event Record - GMER
>> + * CXL rev 3.0 section 8.2.9.2.1.1; Table 8-43
>> + */
>> +struct cper_sec_gen_media {
>> + struct common_event_record record;
>> + u64 dpa;
>> + u8 descriptor;
>> + u8 type;
>> + u8 transaction_type;
>> + u16 validity_flags;
>> + u8 channel;
>> + u8 rank;
>> + u8 device[3];
>> + u8 comp_id[16];
>> + u8 reserved[46];
>> +};
>> +
>
> [snip]
next prev parent reply other threads:[~2023-10-17 20:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 23:02 [PATCH 0/3] efi/cper, cxl: Decode CXL Component Events CPER Smita Koralahalli
2023-10-12 23:02 ` [PATCH 1/3] efi/cper, cxl: Decode CXL Component Events General Media Event Record Smita Koralahalli
2023-10-12 23:26 ` Dan Williams
2023-10-17 20:45 ` Smita Koralahalli
2023-10-13 0:25 ` Ira Weiny
2023-10-17 20:52 ` Smita Koralahalli [this message]
2023-10-18 8:56 ` Ard Biesheuvel
2023-10-18 18:48 ` Dan Williams
2023-10-19 20:52 ` Ard Biesheuvel
2023-10-12 23:03 ` [PATCH 2/3] efi/cper, cxl: Decode CXL Component Events DRAM " Smita Koralahalli
2023-10-12 23:03 ` [PATCH 3/3] efi/cper, cxl: Decode CXL Component Events Memory Module " Smita Koralahalli
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=d5882c60-6636-f651-2886-02c433f77ae1@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=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