From: Shenming Lu <lushenming@huawei.com>
To: Alex Williamson <alex.williamson@redhat.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
Cornelia Huck <cohuck@redhat.com>, <qemu-devel@nongnu.org>,
<qemu-arm@nongnu.org>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Neo Jia <cjia@nvidia.com>,
mst@redhat.com, Marc Zyngier <maz@kernel.org>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Eric Auger <eric.auger@redhat.com>,
yuzenghui@huawei.com, wanghaibin.wang@huawei.com,
lushenming@huawei.com
Subject: [PATCH v4 0/3] vfio: Some fixes and optimizations for VFIO migration
Date: Wed, 10 Mar 2021 11:02:30 +0800 [thread overview]
Message-ID: <20210310030233.1133-1-lushenming@huawei.com> (raw)
This patch set includes two fixes and one optimization for VFIO migration
as blew:
Patch 1-2:
- Fix two ordering problems in migration.
Patch 3:
- Optimize the enabling process of the MSI-X vectors in migration.
History:
v3 -> v4
- Use msix_function_masked instead of msix_masked() in Patch 3.
v2 -> v3:
- Nit fixes.
- Set error in migration stream for migration to fail in Patch 1.
- Tested Patch 3 with a Windows guest.
Thanks,
Shenming
Shenming Lu (3):
vfio: Move the saving of the config space to the right place in VFIO
migration
vfio: Set the priority of the VFIO VM state change handler explicitly
vfio: Avoid disabling and enabling vectors repeatedly in VFIO
migration
hw/vfio/migration.c | 28 +++++++++++++++++-----------
hw/vfio/pci.c | 20 +++++++++++++++++---
2 files changed, 34 insertions(+), 14 deletions(-)
--
2.19.1
next reply other threads:[~2021-03-10 3:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 3:02 Shenming Lu [this message]
2021-03-10 3:02 ` [PATCH v4 1/3] vfio: Move the saving of the config space to the right place in VFIO migration Shenming Lu
2021-03-10 3:02 ` [PATCH v4 2/3] vfio: Set the priority of the VFIO VM state change handler explicitly Shenming Lu
2021-03-10 3:02 ` [PATCH v4 3/3] vfio: Avoid disabling and enabling vectors repeatedly in VFIO migration Shenming Lu
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=20210310030233.1133-1-lushenming@huawei.com \
--to=lushenming@huawei.com \
--cc=alex.williamson@redhat.com \
--cc=cjia@nvidia.com \
--cc=cohuck@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eric.auger@redhat.com \
--cc=kwankhede@nvidia.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=maz@kernel.org \
--cc=mst@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=wanghaibin.wang@huawei.com \
--cc=yuzenghui@huawei.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).