linux-kernel - Re: [PATCH v6 4/6] cxl/events: Update DRAM Event Record to CXL spec rev 3.1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <67853dacb9a2_1817af294c3@iweiny-mobl.notmuch>
Date: Mon, 13 Jan 2025 10:22:04 -0600
From: Ira Weiny <ira.weiny@...el.com>
To: <shiju.jose@...wei.com>, <dave.jiang@...el.com>,
	<dan.j.williams@...el.com>, <jonathan.cameron@...wei.com>,
	<alison.schofield@...el.com>, <nifan.cxl@...il.com>,
	<vishal.l.verma@...el.com>, <ira.weiny@...el.com>, <dave@...olabs.net>,
	<linux-cxl@...r.kernel.org>
CC: <linux-kernel@...r.kernel.org>, <linuxarm@...wei.com>,
	<tanxiaofei@...wei.com>, <prime.zeng@...ilicon.com>, <shiju.jose@...wei.com>
Subject: Re: [PATCH v6 4/6] cxl/events: Update DRAM Event Record to CXL spec
 rev 3.1

shiju.jose@ wrote:
> From: Shiju Jose <shiju.jose@...wei.com>
> 
> CXL spec 3.1 section 8.2.9.2.1.2 Table 8-46, DRAM Event Record has updated
> with following new fields and new types for Memory Event Type, Transaction
> Type and Validity Flags fields.
> 1. Component Identifier
> 2. Sub-channel
> 3. Advanced Programmable Corrected Memory Error Threshold Event Flags
> 4. Corrected Memory Error Count at Event
> 5. Memory Event Sub-Type
> 
> Update DRAM events record and DRAM trace event for the above spec
> changes. The new fields are inserted in logical places.
> Includes trivial consistency of white space improvements.
> 
> Example trace print of cxl_dram trace event,
> 
> cxl_dram: memdev=mem0 host=0000:0f:00.0 serial=3 log=Informational : \
> time=54799339519 uuid=601dcbb3-9c06-4eab-b8af-4e9bfb5c9624 len=128 \
> flags='0x1' handle=1 related_handle=0 maint_op_class=1 \
> maint_op_sub_class=3 : dpa=18680 dpa_flags='' \
> descriptor='UNCORRECTABLE_EVENT|THRESHOLD_EVENT' type='Data Path Error' \
> sub_type='Media Link CRC Error' transaction_type='Internal Media Scrub' \
> channel=3 rank=17 nibble_mask=3b00b2 bank_group=7 bank=11 row=2 \
> column=77 cor_mask=21 00 00 00 00 00 00 00 2c 00 00 00 00 00 00 00 37 00 \
> 00 00 00 00 00 00 42 00 00 00 00 00 00 00 validity_flags='CHANNEL|RANK|NIBBLE|\
> BANK GROUP|BANK|ROW|COLUMN|CORRECTION MASK|COMPONENT|COMPONENT PLDM FORMAT' \
> comp_id=01 74 c5 08 9a 1a 0b fc d2 7e 2f 31 9b 3c 81 4d \
> comp_id_pldm_valid_flags='PLDM Entity ID' pldm_entity_id=74 c5 08 9a 1a 0b \
> pldm_resource_id=0x00 hpa=ffffffffffffffff region= \
> region_uuid=00000000-0000-0000-0000-000000000000 sub_channel=5 \
> cme_threshold_ev_flags='Corrected Memory Errors in Multiple Media Components|\
> Exceeded Programmable Threshold' cvme_count=148
> 
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@...wei.com>
> Reviewed-by: Davidlohr Bueso <dave@...olabs.net>

Reviewed-by: Ira Weiny <ira.weiny@...el.com>