From: Jonathan Cameron via qemu development <qemu-devel@nongnu.org>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>, <qemu-devel@nongnu.org>,
"Cleber Rosa" <crosa@redhat.com>, John Snow <jsnow@redhat.com>
Subject: Re: [PATCH v2 02/13] scripts/qmp_helper: add missing CXL UEFI GUID
Date: Fri, 23 Jan 2026 14:12:09 +0000 [thread overview]
Message-ID: <20260123141209.00007326@huawei.com> (raw)
In-Reply-To: <a1dde4d9549539af805ac171a5ed76c8fd859acf.1769175069.git.mchehab+huawei@kernel.org>
On Fri, 23 Jan 2026 14:35:16 +0100
Mauro Carvalho Chehab <mchehab+huawei@kernel.org> wrote:
> The UEFI 2.11 - N.2.14. CXL Component Events Section states that
> CXL events are described at CXL specification 3.2:
> 8.2.10.2.1 Event Records
> Table 8-55. Common Event Record Format
>
> Add the GUIDs defined here to fuzzy logic error injection code.
>
> It should be noticed that, while the section states that:
>
> "This section defines the standard event record format
> that all CXL devices shall use when reporting events
> to the host."
>
> And the field at byte offset 0 has all the GUIDs below, in practice,
> not all those events will reach the OSPM, as some are fabric
> management events and OS management flows for dynamic capacity.
>
> Yet, it is easier to keep the table in sync with the specs than to
> filter them out and justify why they won't need within CPER scope.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Reviewed-by: Jonathan Cameron <jonathan.cameron@huawei.com>
next prev parent reply other threads:[~2026-01-23 14:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-23 13:35 [PATCH v2 00/13] Add more commands to scripts/ghes_inject.py Mauro Carvalho Chehab
2026-01-23 13:35 ` [PATCH v2 01/13] scripts/qmp_helper: add a return code to send_cper Mauro Carvalho Chehab
2026-01-23 13:35 ` [PATCH v2 02/13] scripts/qmp_helper: add missing CXL UEFI GUID Mauro Carvalho Chehab
2026-01-23 14:12 ` Jonathan Cameron via qemu development [this message]
2026-01-23 13:35 ` [PATCH v2 03/13] scripts/qmp_helper: add support for FRU Memory Poison Mauro Carvalho Chehab
2026-01-23 13:35 ` [PATCH v2 04/13] scripts/qmp_helper: make send_cper() more generic Mauro Carvalho Chehab
2026-01-23 13:35 ` [PATCH v2 05/13] scripts/qmp_helper: fix raw_data logic Mauro Carvalho Chehab
2026-01-23 13:35 ` [PATCH v2 06/13] scripts/qmp_helper: add support for a timeout logic Mauro Carvalho Chehab
2026-01-23 16:17 ` Jonathan Cameron via qemu development
2026-01-23 13:35 ` [PATCH v2 07/13] scripts/ghes_inject: add a logic to decode CPER Mauro Carvalho Chehab
2026-01-23 16:31 ` Jonathan Cameron via qemu development
2026-01-23 13:35 ` [PATCH v2 08/13] scripts/ghes_inject: exit 1 if command was not sent Mauro Carvalho Chehab
2026-01-23 13:35 ` [PATCH v2 09/13] scripts/ghes_inject: add a handler for PCI/PCI-X bus error Mauro Carvalho Chehab
2026-02-20 18:01 ` Michael S. Tsirkin
2026-01-23 13:35 ` [PATCH v2 10/13] scripts/ghes_inject: add support for fuzzy logic testing Mauro Carvalho Chehab
2026-01-23 16:32 ` Jonathan Cameron via qemu development
2026-02-20 18:01 ` Michael S. Tsirkin
2026-01-23 13:35 ` [PATCH v2 11/13] scripts/ghes_inject: add a raw error inject command Mauro Carvalho Chehab
2026-02-20 18:02 ` Michael S. Tsirkin
2026-01-23 13:35 ` [PATCH v2 12/13] scripts/ghes_inject: print help if no command specified Mauro Carvalho Chehab
2026-01-23 16:33 ` Jonathan Cameron via qemu development
2026-01-23 13:35 ` [PATCH v2 13/13] scripts/ghes_inject: improve help message Mauro Carvalho Chehab
2026-02-20 18:03 ` [PATCH v2 00/13] Add more commands to scripts/ghes_inject.py Michael S. Tsirkin
2026-02-23 11:39 ` Mauro Carvalho Chehab
2026-02-23 15:06 ` Michael S. Tsirkin
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=20260123141209.00007326@huawei.com \
--to=qemu-devel@nongnu.org \
--cc=crosa@redhat.com \
--cc=jonathan.cameron@huawei.com \
--cc=jsnow@redhat.com \
--cc=mchehab+huawei@kernel.org \
--cc=mst@redhat.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.