From: Zhenzhong Duan <zhenzhong.duan@intel.com>
To: qemu-devel@nongnu.org
Cc: alex.williamson@redhat.com, clg@redhat.com,
eric.auger@redhat.com, steven.sistare@oracle.com,
Zhenzhong Duan <zhenzhong.duan@intel.com>
Subject: [PATCH v2 0/6] VFIO: cpr-transfer fixes
Date: Sun, 28 Sep 2025 04:54:26 -0400 [thread overview]
Message-ID: <20250928085432.40107-1-zhenzhong.duan@intel.com> (raw)
Hi,
Patch1: fixed an error restore path when virtio-mem is configured.
Patch2: fixed assert failure on error restore path, this issue happens
no matter if virtio-mem is configured.
Some trick is played to trigger the error path,
see https://github.com/yiliu1765/qemu/commit/494d19e7f7242dbc47d7f236937cde0c396a4a7c
Patch3-4: issue only happens with two or more VFIO devices, no issue
if only one VFIO device.
Patch5: fix a bug that impact "query-balloon" execution
Patch6: SIGSEGV if I send "query-balloon" to source qmp monitor,
I'm not quite sure if it's deserved to be fixed, as guest has been
migrated to destination, it's not a big issue for source qemu to
SIGSEGV?
Thanks
Zhenzhong
Changelog:
v2:
- minor polishment to commit log (Steve)
- keep kvm_state so "query-balloon" could work after CPR-transfer (Markus)
- add a fix which is found during "query-balloon" execution
- rebased to master
Zhenzhong Duan (6):
vfio/container: Remap only populated parts in a section
vfio/cpr-legacy: drop an erroneous assert
vfio/iommufd: Set cpr.ioas_id on source side for CPR transfer
vfio/iommufd: Restore vbasedev's reference to hwpt after CPR transfer
accel/kvm: Fix an erroneous check on coalesced_mmio_ring
accel/kvm: Fix SIGSEGV when execute "query-balloon" after CPR transfer
include/hw/vfio/vfio-cpr.h | 2 +-
accel/kvm/kvm-all.c | 14 ++++++--------
hw/vfio/cpr-legacy.c | 22 +++++++++++++++-------
hw/vfio/iommufd.c | 8 ++++----
hw/vfio/listener.c | 4 ++--
5 files changed, 28 insertions(+), 22 deletions(-)
--
2.47.1
next reply other threads:[~2025-09-28 8:56 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-28 8:54 Zhenzhong Duan [this message]
2025-09-28 8:54 ` [PATCH v2 1/6] vfio/container: Remap only populated parts in a section Zhenzhong Duan
2025-09-28 8:54 ` [PATCH v2 2/6] vfio/cpr-legacy: drop an erroneous assert Zhenzhong Duan
2025-09-28 8:54 ` [PATCH v2 3/6] vfio/iommufd: Set cpr.ioas_id on source side for CPR transfer Zhenzhong Duan
2025-09-28 8:54 ` [PATCH v2 4/6] vfio/iommufd: Restore vbasedev's reference to hwpt after " Zhenzhong Duan
2025-09-28 8:54 ` [PATCH v2 5/6] accel/kvm: Fix an erroneous check on coalesced_mmio_ring Zhenzhong Duan
2025-09-29 13:34 ` Steven Sistare
2025-09-28 8:54 ` [PATCH v2 6/6] accel/kvm: Fix SIGSEGV when execute "query-balloon" after CPR transfer Zhenzhong Duan
2025-09-29 13:54 ` Steven Sistare
2025-09-30 6:00 ` Duan, Zhenzhong
2025-09-30 12:52 ` Steven Sistare
2025-10-08 10:22 ` Duan, Zhenzhong
2025-10-09 14:11 ` Steven Sistare
2025-10-09 14:19 ` Daniel P. Berrangé
2025-10-09 14:32 ` Steven Sistare
2025-10-09 14:36 ` Daniel P. Berrangé
2025-10-10 3:54 ` Duan, Zhenzhong
2025-10-10 8:39 ` Daniel P. Berrangé
2025-10-10 3:45 ` Duan, Zhenzhong
2025-10-10 3:39 ` Duan, Zhenzhong
2025-10-07 15:39 ` [PATCH v2 0/6] VFIO: cpr-transfer fixes Cédric Le Goater
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=20250928085432.40107-1-zhenzhong.duan@intel.com \
--to=zhenzhong.duan@intel.com \
--cc=alex.williamson@redhat.com \
--cc=clg@redhat.com \
--cc=eric.auger@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=steven.sistare@oracle.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;
as well as URLs for NNTP newsgroup(s).