From: Markus Armbruster <armbru@redhat.com>
To: shiju.jose--- via <qemu-devel@nongnu.org>
Cc: <linux-cxl@vger.kernel.org>, <jonathan.cameron@huawei.com>,
<fan.ni@samsung.com>, <dave@stgolabs.net>,
<shiju.jose@huawei.com>, <linuxarm@huawei.com>
Subject: Re: [PATCH qemu v4 4/7] hw/cxl/events: Updates for rev3.2 memory module event record
Date: Wed, 06 Aug 2025 10:08:27 +0200 [thread overview]
Message-ID: <874iukq3d0.fsf@pond.sub.org> (raw)
In-Reply-To: <20250721172228.2118-5-shiju.jose@huawei.com> (shiju jose's message of "Mon, 21 Jul 2025 18:22:25 +0100")
shiju.jose--- via <qemu-devel@nongnu.org> 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.
>
> Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> Signed-off-by: Shiju Jose <shiju.jose@huawei.com>
[...]
> diff --git a/qapi/cxl.json b/qapi/cxl.json
> index f84088c0b9..118dec5362 100644
> --- a/qapi/cxl.json
> +++ b/qapi/cxl.json
> @@ -261,6 +261,16 @@
> # @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.
> +# See CXL r3.2 Table 8-59 Memory Module Event Record.
> +#
> +# @is-comp-id-pldm: Flag represents device specific component identifier
> +# format is PLDM or not.
> +#
> +# @sub-type: Device event sub-type.
> +# See CXL r3.2 Table 8-59 Memory Module Event Record.
> +#
> # Since: 8.1
> ##
> { 'command': 'cxl-inject-memory-module-event',
Again, partial copy of stuff the previous two patches added to related
commands.
> @@ -272,7 +282,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':'uint8',
> + 'sub-type':'uint8'
> }}
>
> ##
next prev parent reply other threads:[~2025-08-06 8:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-21 17:22 [PATCH qemu v4 0/7] hw/cxl: Update CXL events to rev3.2 and add maintenance support for memory repair features shiju.jose
2025-07-21 17:22 ` shiju.jose--- via
2025-07-21 17:22 ` [PATCH qemu v4 1/7] hw/cxl/events: Update for rev3.2 common event record format shiju.jose
2025-07-21 17:22 ` shiju.jose--- via
2025-07-25 12:45 ` Jonathan Cameron
2025-07-25 12:45 ` Jonathan Cameron via
2025-08-06 7:45 ` Markus Armbruster
2025-07-21 17:22 ` [PATCH qemu v4 2/7] hw/cxl/events: Updates for rev3.2 general media event record shiju.jose
2025-07-21 17:22 ` shiju.jose--- via
2025-08-06 7:57 ` Markus Armbruster
2025-08-06 9:21 ` Shiju Jose
2025-08-06 9:21 ` Shiju Jose via
2025-08-06 10:23 ` Markus Armbruster
2025-07-21 17:22 ` [PATCH qemu v4 3/7] hw/cxl/events: Updates for rev3.2 DRAM " shiju.jose
2025-07-21 17:22 ` shiju.jose--- via
2025-08-06 8:05 ` Markus Armbruster
2025-07-21 17:22 ` [PATCH qemu v4 4/7] hw/cxl/events: Updates for rev3.2 memory module " shiju.jose
2025-07-21 17:22 ` shiju.jose--- via
2025-08-06 8:08 ` Markus Armbruster [this message]
2025-07-21 17:22 ` [PATCH qemu v4 5/7] hw/cxl/cxl-mailbox-utils: Move declaration of scrub and ECS feature attributes in cmd_features_set_feature() shiju.jose
2025-07-21 17:22 ` shiju.jose--- via
2025-07-21 17:22 ` [PATCH qemu v4 6/7] hw/cxl: Add Maintenance support shiju.jose
2025-07-21 17:22 ` shiju.jose--- via
2025-07-25 13:26 ` Jonathan Cameron
2025-07-25 13:26 ` Jonathan Cameron via
2025-07-21 17:22 ` [PATCH qemu v4 7/7] hw/cxl: Add emulation for memory sparing control feature shiju.jose
2025-07-21 17:22 ` shiju.jose--- via
2025-07-25 13:31 ` Jonathan Cameron
2025-07-25 13:31 ` Jonathan Cameron via
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=874iukq3d0.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=shiju.jose@huawei.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.