From: Markus Armbruster <armbru@redhat.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: Michael Tsirkin <mst@redhat.com>, <qemu-devel@nongnu.org>,
<shiju.jose@huawei.com>, <armbru@redhat.com>,
<linuxarm@huawei.com>, <linux-cxl@vger.kernel.org>,
Ravi Shankar <venkataravis@micron.com>
Subject: Re: [PATCH qemu v3 5/5] hw/cxl/events: Updates for rev3.2 memory module event record
Date: Wed, 14 Jan 2026 19:33:41 +0100 [thread overview]
Message-ID: <87o6mwyrga.fsf@pond.sub.org> (raw)
In-Reply-To: <20260114142713.617806-6-Jonathan.Cameron@huawei.com> (Jonathan Cameron's message of "Wed, 14 Jan 2026 14:27:13 +0000")
Jonathan Cameron <Jonathan.Cameron@huawei.com> writes:
> From: Shiju Jose <shiju.jose@huawei.com>
>
> CXL spec rev3.2 section 8.2.10.2.1.3 Table 8-50, memory module
> event record has updated with following new fields.
> 1. Validity Flags
> 2. Component Identifier
> 3. Device Event Sub-Type
>
> Add updates for the above spec changes in the CXL memory module
> event reporting and QMP command to inject memory module event.
>
> Updated all references for this command to the CXL r3.2
> specification.
>
> Signed-off-by: Shiju Jose <shiju.jose@huawei.com>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> ---
> V3: Update spec references for whole command (Markus)
> ---
> qapi/cxl.json | 26 ++++++++++++++++++--------
> include/hw/cxl/cxl_events.h | 7 +++++--
> hw/mem/cxl_type3.c | 20 ++++++++++++++++++++
> hw/mem/cxl_type3_stubs.c | 4 ++++
> 4 files changed, 47 insertions(+), 10 deletions(-)
>
> diff --git a/qapi/cxl.json b/qapi/cxl.json
> index 630c37d64eed..fc2ff2e080b4 100644
> --- a/qapi/cxl.json
> +++ b/qapi/cxl.json
> @@ -214,20 +214,20 @@
> ##
> # @CXLMemModuleEvent:
> #
> -# Event record for a Memory Module Event (CXL r3.0 8.2.9.2.1.3).
> +# Event record for a Memory Module Event (CXL r3.2 8.2.10.2.1.3).
> #
> -# @type: Device Event Type. See CXL r3.0 Table 8-45 Memory Module
> +# @type: Device Event Type. See CXL r3.2 Table 8-59 Memory Module
> # Event Record for bit definitions for bit definiions.
> #
> -# @health-status: Overall health summary bitmap. See CXL r3.0 Table
> -# 8-100 Get Health Info Output Payload, Health Status for bit
> +# @health-status: Overall health summary bitmap. See CXL r3.2 Table
> +# 8-148 Get Health Info Output Payload, Health Status for bit
> # definitions.
> #
> -# @media-status: Overall media health summary. See CXL r3.0 Table
> -# 8-100 Get Health Info Output Payload, Media Status for bit
> +# @media-status: Overall media health summary. See CXL r3.2 Table
> +# 8-148 Get Health Info Output Payload, Media Status for bit
> # definitions.
> #
> -# @additional-status: See CXL r3.0 Table 8-100 Get Health Info Output
> +# @additional-status: See CXL r3.2 Table 8-148 Get Health Info Output
> # Payload, Additional Status for subfield definitions.
> #
> # @life-used: Percentage (0-100) of factory expected life span.
> @@ -243,6 +243,14 @@
> # @corrected-persistent-error-count: Total number of correctable
> # errors in persistent memory
> #
> +# @component-id: Device specific component identifier for the event.
> +# May describe a field replaceable sub-component of the device.
> +#
> +# @is-comp-id-pldm: This flag specifies whether the device-specific
> +# component identifier format follows PLDM.
> +#
> +# @sub-type: Device event sub-type.
> +#
> # Since: 8.1
> ##
> { 'struct': 'CXLMemModuleEvent',
> @@ -252,7 +260,9 @@
> 'life-used': 'uint8', 'temperature' : 'int16',
> 'dirty-shutdown-count': 'uint32',
> 'corrected-volatile-error-count': 'uint32',
> - 'corrected-persistent-error-count': 'uint32'
> + 'corrected-persistent-error-count': 'uint32',
> + '*component-id': 'str', '*is-comp-id-pldm':'bool',
> + 'sub-type':'uint8'
> }}
>
> ##
# @cxl-inject-memory-module-event:
#
# Inject an event record for a Memory Module Event (CXL r3.0
# 8.2.9.2.1.3). This event includes a copy of the Device Health info
Should we update this reference as well?
# at the time of the event.
#
# Since: 8.1
##
{ 'command': 'cxl-inject-memory-module-event',
'data': 'CXLMemModuleEvent' }
[...]
prev parent reply other threads:[~2026-01-14 18:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 14:27 [PATCH qemu v3 0/5] cxl: r3.2 specification event updates Jonathan Cameron
2026-01-14 14:27 ` Jonathan Cameron via qemu development
2026-01-14 14:27 ` [PATCH qemu v3 1/5] qapi: cxl: Refactor CXL event injection for common commands arguments Jonathan Cameron
2026-01-14 14:27 ` Jonathan Cameron via qemu development
2026-01-14 14:27 ` [PATCH qemu v3 2/5] hw/cxl/events: Update for rev3.2 common event record format Jonathan Cameron
2026-01-14 14:27 ` Jonathan Cameron via qemu development
2026-01-14 14:27 ` [PATCH qemu v3 3/5] hw/cxl/events: Updates for rev3.2 general media event record Jonathan Cameron
2026-01-14 14:27 ` Jonathan Cameron via qemu development
2026-01-14 18:32 ` Markus Armbruster
2026-01-14 14:27 ` [PATCH qemu v3 4/5] hw/cxl/events: Updates for rev3.2 DRAM " Jonathan Cameron
2026-01-14 14:27 ` Jonathan Cameron via qemu development
2026-01-14 18:33 ` Markus Armbruster
2026-01-14 14:27 ` [PATCH qemu v3 5/5] hw/cxl/events: Updates for rev3.2 memory module " Jonathan Cameron
2026-01-14 14:27 ` Jonathan Cameron via qemu development
2026-01-14 18:33 ` Markus Armbruster [this message]
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=87o6mwyrga.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shiju.jose@huawei.com \
--cc=venkataravis@micron.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.