From: Hyeonggon Yoo <42.hyeyoo@gmail.com>
To: Jonathan Cameron <jonathan.cameron@huawei.com>,
Fan Ni <fan.ni@samsung.com>,
"Michael S . Tsirkin" <mst@redhat.com>
Cc: linux-cxl@lore.kernel.org, qemu-devel@nongnu.org,
Davidlohr Bueso <dave@stgolabs.net>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>
Subject: [PATCH v1 0/2] A Fixup for "QEMU: CXL mailbox rework and features (Part 1)"
Date: Mon, 27 Nov 2023 19:58:28 +0900 [thread overview]
Message-ID: <20231127105830.2104954-1-42.hyeyoo@gmail.com> (raw)
Hi, this is a fixup for the recent patch series "QEMU: CXL mailbox rework and
features (Part 1)" [1].
This fixes two problems:
1. Media Status in memory device status register not being correctly
read as "Disabled" while sanitation is in progress.
2. QEMU assertion failure when it issues an MSI-X interrupt
(indicating the completion of the sanitize command).
[1] https://lore.kernel.org/linux-cxl/20231023160806.13206-1-Jonathan.Cameron@huawei.com
Hyeonggon Yoo (2):
hw/cxl/device: read from register values in mdev_reg_read()
hw/mem/cxl_type3: allocate more vectors for MSI-X
hw/cxl/cxl-device-utils.c | 17 +++++++++++------
hw/mem/cxl_type3.c | 2 +-
include/hw/cxl/cxl_device.h | 4 +++-
3 files changed, 15 insertions(+), 8 deletions(-)
--
2.39.1
next reply other threads:[~2023-11-27 10:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 10:58 Hyeonggon Yoo [this message]
2023-11-27 10:58 ` [PATCH v1 1/2] hw/cxl/device: read from register values in mdev_reg_read() Hyeonggon Yoo
2023-11-27 20:27 ` Davidlohr Bueso
2023-11-28 0:42 ` Hyeonggon Yoo
2023-11-28 5:42 ` Davidlohr Bueso
2023-11-30 16:32 ` Jonathan Cameron via
2023-12-04 3:38 ` Davidlohr Bueso
2023-11-27 10:58 ` [PATCH v1 2/2] hw/mem/cxl_type3: allocate more vectors for MSI-X Hyeonggon Yoo
2023-11-27 17:53 ` Davidlohr Bueso
2023-11-28 0:27 ` Hyeonggon Yoo
2023-11-28 12:46 ` Jonathan Cameron via
2023-11-30 5:53 ` Hyeonggon Yoo
2023-11-28 7:31 ` [PATCH v1 0/2] A Fixup for "QEMU: CXL mailbox rework and features (Part 1)" Michael S. Tsirkin
2023-11-29 7:40 ` Hyeonggon Yoo
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=20231127105830.2104954-1-42.hyeyoo@gmail.com \
--to=42.hyeyoo@gmail.com \
--cc=dave@stgolabs.net \
--cc=fan.ni@samsung.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@lore.kernel.org \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).