From: Zhenzhong Duan <zhenzhong.duan@intel.com>
To: qemu-devel@nongnu.org
Cc: alex.williamson@redhat.com, clg@redhat.com,
joao.m.martins@oracle.com, avihaih@nvidia.com,
chao.p.peng@intel.com
Subject: [PATCH v5 0/7] VFIO migration related refactor and bug fix
Date: Fri, 30 Jun 2023 15:36:32 +0800 [thread overview]
Message-ID: <20230630073637.124234-1-zhenzhong.duan@intel.com> (raw)
Hello,
PATCH4,5,7 refactors the VFIO migration blocker related code based on
suggestions from Joao and Cedric, so that code is simpler and
redundant "Migration disabled" isn't printed.
But before that works, also found some hotplug bugs when testing
blocker adding failed case. PATCH1-3,6 fix them.
See patch description for details.
v5: PATCH1-2 are not sent in v5 as Cedric already picked them
Minor adjust on PATCH3 per Joao and Cedric
Move PATCH4 after refactor patch per Joao
Split refactor patch to three patches, PATCH4,5,7
v4: Rebased on [1] which contains Avihai's patchset [2]
Add more patches to fix resource leak issue, split based on
different fix TAG per Joao
Change to not print "Migration disabled" with explicit
enable-migration=off per Avihai
Rename vfio_block_giommu_migration to vfio_viommu_preset per Joao
v3: Add PATCH1,2 to fix hotplug bug
Fix bugs in PATCH3 Avihai and Joao pointed out
Tested vfio hotplug/unplug with vfio migration supported and unsupported cases,
and different param of enable-migration=[on/off/auto] and -only-migratable.
[1] https://github.com/legoater/qemu/tree/vfio-next
[2] https://lists.nongnu.org/archive/html/qemu-devel/2023-06/msg06117.html
Thanks
Zhenzhong Duan (5):
vfio/pci: Disable INTx in vfio_realize error path
vfio/migration: Return bool type for some vfio migration related
functions
vfio/migration: Change vIOMMU blocker from global to per device
vfio/migration: Free resources when vfio_migration_realize fails
vfio/migration: Remove print of "Migration disabled"
hw/vfio/common.c | 59 ++++-------------------------------
hw/vfio/migration.c | 59 +++++++++++++++++++++++------------
hw/vfio/pci.c | 8 +++--
include/hw/vfio/vfio-common.h | 7 ++---
4 files changed, 53 insertions(+), 80 deletions(-)
--
2.34.1
next reply other threads:[~2023-06-30 7:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 7:36 Zhenzhong Duan [this message]
2023-06-30 7:36 ` [PATCH v5 3/7] vfio/pci: Disable INTx in vfio_realize error path Zhenzhong Duan
2023-06-30 9:41 ` Joao Martins
2023-07-03 6:28 ` Cédric Le Goater
2023-06-30 7:36 ` [PATCH v5 4/7] vfio/migration: Return bool type for some vfio migration related functions Zhenzhong Duan
2023-06-30 10:41 ` Joao Martins
2023-07-03 6:26 ` Duan, Zhenzhong
2023-06-30 7:36 ` [PATCH v5 5/7] vfio/migration: Change vIOMMU blocker from global to per device Zhenzhong Duan
2023-06-30 11:17 ` Joao Martins
2023-07-03 6:06 ` Duan, Zhenzhong
2023-06-30 7:36 ` [PATCH v5 6/7] vfio/migration: Free resources when vfio_migration_realize fails Zhenzhong Duan
2023-06-30 7:36 ` [PATCH v5 7/7] vfio/migration: Remove print of "Migration disabled" Zhenzhong Duan
2023-06-30 11:20 ` Joao Martins
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=20230630073637.124234-1-zhenzhong.duan@intel.com \
--to=zhenzhong.duan@intel.com \
--cc=alex.williamson@redhat.com \
--cc=avihaih@nvidia.com \
--cc=chao.p.peng@intel.com \
--cc=clg@redhat.com \
--cc=joao.m.martins@oracle.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).