From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Michael Tsirkin <mst@redhat.com>, <qemu-devel@nongnu.org>,
<shiju.jose@huawei.com>, Ravi Shankar <venkataravis@micron.com>,
<armbru@redhat.com>, Ravi Jonnalagadda <ravis.opensrc@gmail.com>
Cc: <linuxarm@huawei.com>, <linux-cxl@vger.kernel.org>
Subject: [PATCH qemu v5 0/5] cxl: r3.2 specification event updates.
Date: Thu, 5 Feb 2026 11:23:45 +0000 [thread overview]
Message-ID: <20260205112350.60681-1-Jonathan.Cameron@huawei.com> (raw)
Changes since v4:
- Fix the setting of descriptor field in general media and DRAM event records.
(Ravi)
- Fix wrong table number in the commit description for patch 5.
Chances since v3:
https://lore.kernel.org/qemu-devel/20260114142713.617806-1-Jonathan.Cameron@huawei.com/
Update references in the documentation for related commands as well as the
structures. (Markus)
Changes since v2:
https://lore.kernel.org/all/20260102151512.460766-1-Jonathan.Cameron@huawei.com/
Thanks to Markus Armbruster.
- Expand LD acronym. Given the spec definition is acronyms soup, just
expand to Logical Device and let people go enjoy the specification if
they want to know what that actually means!
- Update spec references elsewhere in the qapi commands and data types
so they all refer to r3.2 rather than just the new bits.
v2: Cover letter,
Hi Michael,
This is a rebase/resend of:
https://lore.kernel.org/qemu-devel/20250917141355.293217-1-Jonathan.Cameron@huawei.com/
which I think slipped through the cracks for 10.2.
Original cover letter:
This is the 1st CXL set that I think is ready for upstream.
They are lightly tweaked and rebased from the first part of:
https://lore.kernel.org/qemu-devel/20250811085530.2263-1-shiju.jose@huawei.com/
[PATCH v6 0/8] hw/cxl: Update CXL events to rev3.2 and add maintenance support for memory repair features
I've split that series up as the two parts were only slightly connected.
The initial rework was a request from Markus from an earlier version.
Shiju Jose (5):
qapi: cxl: Refactor CXL event injection for common commands arguments
hw/cxl/events: Update for rev3.2 common event record format
hw/cxl/events: Updates for rev3.2 general media event record
hw/cxl/events: Updates for rev3.2 DRAM event record
hw/cxl/events: Updates for rev3.2 memory module event record
qapi/cxl.json | 180 ++++++++++++++++++++++++++----------
include/hw/cxl/cxl_device.h | 7 +-
include/hw/cxl/cxl_events.h | 38 ++++++--
hw/cxl/cxl-events.c | 3 +-
hw/cxl/cxl-mailbox-utils.c | 3 +-
hw/mem/cxl_type3.c | 167 ++++++++++++++++++++++++++++++---
hw/mem/cxl_type3_stubs.c | 41 +++++++-
7 files changed, 364 insertions(+), 75 deletions(-)
--
2.51.0
next reply other threads:[~2026-02-05 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 11:23 Jonathan Cameron [this message]
2026-02-05 11:23 ` [PATCH qemu v5 1/5] qapi: cxl: Refactor CXL event injection for common commands arguments Jonathan Cameron
2026-02-05 11:23 ` [PATCH qemu v5 2/5] hw/cxl/events: Update for rev3.2 common event record format Jonathan Cameron
2026-02-05 11:23 ` [PATCH qemu v5 3/5] hw/cxl/events: Updates for rev3.2 general media event record Jonathan Cameron
2026-02-05 11:23 ` [PATCH qemu v5 4/5] hw/cxl/events: Updates for rev3.2 DRAM " Jonathan Cameron
2026-02-05 11:23 ` [PATCH qemu v5 5/5] hw/cxl/events: Updates for rev3.2 memory module " Jonathan Cameron
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=20260205112350.60681-1-Jonathan.Cameron@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=armbru@redhat.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=ravis.opensrc@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox