Re: [PATCH 11/13] rasdaemon: ras-mc-ctl: Update logging of CXL general media event data to align with CXL spec rev 3.1
From: Jonathan Cameron
Date: Thu Nov 21 2024 - 10:38:09 EST
On Wed, 20 Nov 2024 09:59:21 +0000
<shiju.jose@xxxxxxxxxx> wrote:
> From: Shiju Jose <shiju.jose@xxxxxxxxxx>
>
> CXL spec rev 3.1 section 8.2.9.2.1.1 Table 8-45, General Media Event
> Record has updated with following new fields and new types for Memory
> Event Type and Transaction Type fields.
> 1. Advanced Programmable Corrected Memory Error Threshold Event Flags
> 2. Corrected Memory Error Count at Event
> 3. Memory Event Sub-Type
>
> The format of component identifier has changed (CXL spec 3.1 section
> 8.2.9.2.1 Table 8-44).
>
> This update modifies ras-mc-ctl to parse and log CXL general media event
> data stored in the RAS SQLite database table, reflecting the specification
> changes introduced in revision 3.1.
>
> Example output,
>
> ./util/ras-mc-ctl --errors
> ...
> CXL general media events:
> 1 2024-11-20 00:00:49 +0000 error: memdev=mem1, host=0000:0f:00.0, \
> serial=0x3, log=Fatal, hdr_uuid=00000000-0000-0000-0000-000000000000, \
> hdr_flags=0x1 , hdr_handle=0x1, hdr_related_handle=0x0, \
> hdr_timestamp=1970-01-01 00:00:49 +0000, hdr_length=128, \
> hdr_maint_op_class=2, hdr_maint_op_sub_class=4, dpa=0x30d40, dpa_flags: , \
> descriptor_flags: 'UNCORRECTABLE EVENT' , 'THRESHOLD EVENT' , \
> 'POISON LIST OVERFLOW' , memory event type: TE State Violation, \
> memory event sub type: Media Link Command Training Error, transaction_type: \
> Host Inject Poison, channel=3, rank=33, device=0x5, \
> component_id:03 74 c5 08 9a 1a 0b fc d2 7e 2f 31 9b 3c 81 4d \
> pldm_entity_id:74 c5 08 9a 1a 0b pldm_resource_id:fc d2 7e 2f \
> hpa=0xffffffffffffffff, region_uuid=00000000-0000-0000-0000-000000000000, \
> cme_threshold_ev_flags: 'Corrected Memory Errors in Multiple Media Components' , \
> 'Exceeded Programmable Threshold' , cme_count=0x78,
> ...
>
> Signed-off-by: Shiju Jose <shiju.jose@xxxxxxxxxx>
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@xxxxxxxxxx>