qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avihai Horon <avihaih@nvidia.com>
To: <qemu-devel@nongnu.org>
Cc: "Alex Williamson" <alex.williamson@redhat.com>,
	"Cédric Le Goater" <clg@redhat.com>,
	"Juan Quintela" <quintela@redhat.com>,
	"Peter Xu" <peterx@redhat.com>,
	"Leonardo Bras" <leobras@redhat.com>,
	"Zhenzhong Duan" <zhenzhong.duan@intel.com>,
	"Yishai Hadas" <yishaih@nvidia.com>,
	"Jason Gunthorpe" <jgg@nvidia.com>,
	"Maor Gottlieb" <maorg@nvidia.com>,
	"Avihai Horon" <avihaih@nvidia.com>,
	"Kirti Wankhede" <kwankhede@nvidia.com>,
	"Tarun Gupta" <targupta@nvidia.com>,
	"Joao Martins" <joao.m.martins@oracle.com>
Subject: [PATCH 0/3] vfio/migration: Make VFIO migration non-experimental
Date: Mon, 26 Jun 2023 11:23:50 +0300	[thread overview]
Message-ID: <20230626082353.18535-1-avihaih@nvidia.com> (raw)

Hello,

The major parts of VFIO migration are supported today in QEMU. This
includes basic VFIO migration, device dirty page tracking and precopy
support. Thus, at this point in time, it seems appropriate to make VFIO
migration non-experimental.

This short series (which is based on the precopy series [1]) does that
and also adds a few improvements:
- Patch #1 moves the transition from STOP_COPY to STOP state to
  vfio_save_cleanup(). Testing with a ConnectX-7 VFIO device showed
  that this can reduce downtime by 6% with loaded devices.
- Patch #2 resets bytes_transferred counter properly.
- Patch #3 cleans up the VFIO migration realize flow and makes VFIO
  migration non-experimental.

Note that Zhenzhong's series [2] fixes additional bugs and further
cleans the VFIO migration realize flow.

Thanks.

[1]
https://lore.kernel.org/qemu-devel/20230621111201.29729-1-avihaih@nvidia.com/

[2]
https://lore.kernel.org/qemu-devel/20230621080204.420723-1-zhenzhong.duan@intel.com/

Avihai Horon (3):
  vfio/migration: Move from STOP_COPY to STOP in vfio_save_cleanup()
  vfio/migration: Reset bytes_transferred properly
  vfio/migration: Make VFIO migration non-experimental

 include/hw/vfio/vfio-common.h |  3 +-
 migration/migration.h         |  1 +
 hw/vfio/migration.c           | 54 ++++++++++++++++++++++-------------
 hw/vfio/pci.c                 |  4 +--
 migration/migration.c         |  1 +
 migration/savevm.c            |  1 +
 migration/target.c            | 17 +++++++++--
 7 files changed, 56 insertions(+), 25 deletions(-)

-- 
2.26.3



             reply	other threads:[~2023-06-26  8:30 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26  8:23 Avihai Horon [this message]
2023-06-26  8:23 ` [PATCH 1/3] vfio/migration: Move from STOP_COPY to STOP in vfio_save_cleanup() Avihai Horon
2023-06-26  9:56   ` Cédric Le Goater
2023-06-26 11:31     ` Avihai Horon
2023-06-26  8:23 ` [PATCH 2/3] vfio/migration: Reset bytes_transferred properly Avihai Horon
2023-06-26  9:52   ` Cédric Le Goater
2023-06-26 11:46     ` Avihai Horon
2023-06-26 12:01       ` Cédric Le Goater
2023-06-26 12:08   ` Avihai Horon
2023-06-26  8:23 ` [PATCH 3/3] vfio/migration: Make VFIO migration non-experimental Avihai Horon
2023-06-26 13:20   ` Cédric Le Goater
2023-06-26 13:40     ` Joao Martins
2023-06-26 15:26       ` Cédric Le Goater
2023-06-26 16:19         ` Jason Gunthorpe
2023-06-26 16:39           ` Cédric Le Goater
2023-06-26 16:36         ` Joao Martins
2023-06-26 17:27         ` Alex Williamson
2023-06-27  8:00           ` Avihai Horon
2023-06-27 12:21             ` Cédric Le Goater
2023-06-27 12:30               ` Jason Gunthorpe
2023-06-28  3:09                 ` Shameerali Kolothum Thodi via
2023-06-27 14:20             ` Alex Williamson

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=20230626082353.18535-1-avihaih@nvidia.com \
    --to=avihaih@nvidia.com \
    --cc=alex.williamson@redhat.com \
    --cc=clg@redhat.com \
    --cc=jgg@nvidia.com \
    --cc=joao.m.martins@oracle.com \
    --cc=kwankhede@nvidia.com \
    --cc=leobras@redhat.com \
    --cc=maorg@nvidia.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=targupta@nvidia.com \
    --cc=yishaih@nvidia.com \
    --cc=zhenzhong.duan@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;
as well as URLs for NNTP newsgroup(s).