From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: <mst@redhat.com>, <qemu-devel@nongnu.org>
Cc: <linux-cxl@vger.kernel.org>,
Markus Armbruster <armbru@redhat.com>,
Li Zhijian <lizhijian@fujitsu.com>, <linuxarm@huawei.com>,
Zhao Liu <zhao1.liu@linux.intel.com>,
Xingtao Yao <yaoxt.fnst@fujitsu.com>
Subject: [PATCH qemu v2 0/3] hw/cxl: Misc minor improvements
Date: Fri, 5 Jul 2024 12:39:53 +0100 [thread overview]
Message-ID: <20240705113956.941732-1-Jonathan.Cameron@huawei.com> (raw)
v2: Switch patch 1 from a patch that removes the cfmws_list element
of CXLState to a fix that makes use of it to fix a crash.
Now based on master as precursors merged.
Before pushing on to more significant features a few unrelated patches
doing tidying up + one to avoid people setting the memory backend both
for a CXL type 3 device and as normal RAM in an attempt to get SRAT to
cover it correctly. We've had multiple 'bug' reports from this and if
nothing else I'd like to stop getting those!
Fan Ni (1):
hw/cxl/cxl-mailbox-utils: remove unneeded mailbox output payload space
zeroing
Jonathan Cameron (1):
hw/cxl: Check for multiple mappings of memory backends.
Zhao Liu (1):
hw/cxl/cxl-host: Fix segmentation fault when getting cxl-fmw property
hw/cxl/cxl-host.c | 3 ++-
hw/cxl/cxl-mailbox-utils.c | 7 -------
hw/mem/cxl_type3.c | 15 +++++++++++++++
3 files changed, 17 insertions(+), 8 deletions(-)
--
2.43.0
next reply other threads:[~2024-07-05 11:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 11:39 Jonathan Cameron [this message]
2024-07-05 11:39 ` [PATCH v2 1/3] hw/cxl/cxl-host: Fix segmentation fault when getting cxl-fmw property Jonathan Cameron
2024-07-24 4:53 ` Michael Tokarev
2024-07-25 16:54 ` Jonathan Cameron
2024-07-05 11:39 ` [PATCH v2 2/3] hw/cxl/cxl-mailbox-utils: remove unneeded mailbox output payload space zeroing Jonathan Cameron
2024-07-05 11:39 ` [PATCH v2 3/3] hw/cxl: Check for multiple mappings of memory backends 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=20240705113956.941732-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=lizhijian@fujitsu.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yaoxt.fnst@fujitsu.com \
--cc=zhao1.liu@linux.intel.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