From: Alex Williamson <alex.williamson@redhat.com>
To: Avihai Horon <avihaih@nvidia.com>
Cc: qemu-devel@nongnu.org, "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>,
"Kirti Wankhede" <kwankhede@nvidia.com>,
"Tarun Gupta" <targupta@nvidia.com>,
"Joao Martins" <joao.m.martins@oracle.com>
Subject: Re: [PATCH v2 0/2] vfio/migration: Make VFIO migration non-experimental
Date: Wed, 28 Jun 2023 15:14:15 -0600 [thread overview]
Message-ID: <20230628151415.77ee583e.alex.williamson@redhat.com> (raw)
In-Reply-To: <20230628073112.7958-1-avihaih@nvidia.com>
On Wed, 28 Jun 2023 10:31:10 +0300
Avihai Horon <avihaih@nvidia.com> wrote:
> 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 resets bytes_transferred counter properly.
> - Patch #2 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.
>
> Changes from v1 [3]:
> * Dropped patch #1 as it's an optimization. (Cedric)
> * Added Fixes tag to patch #2. (Cedric)
> * Made VFIO device realization fail if migration is not supported and
> enable_migration is ON. (Cedric)
> * Kept the error message of errno == ENOTTY case as it was in
> vfio_migration_query_flags(). (Cedric)
> * Added a warn when enable_migration is ON and device dirty tracking is
> not supported. (Alex)
> * Renamed trace_vfio_migration_probe() to
> * trace_vfio_migration_realize().
>
>
> 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/
>
> [3]
> https://lore.kernel.org/qemu-devel/20230626082353.18535-1-avihaih@nvidia.com/
>
> Avihai Horon (2):
> vfio/migration: Reset bytes_transferred properly
> vfio/migration: Make VFIO migration non-experimental
>
> include/hw/vfio/vfio-common.h | 7 +--
> migration/migration.h | 1 +
> hw/vfio/common.c | 16 ++++++-
> hw/vfio/migration.c | 85 ++++++++++++++++++++++++-----------
> hw/vfio/pci.c | 4 +-
> migration/migration.c | 1 +
> migration/savevm.c | 1 +
> migration/target.c | 17 ++++++-
> hw/vfio/trace-events | 2 +-
> 9 files changed, 97 insertions(+), 37 deletions(-)
>
Reviewed-by: Alex Williamson <alex.williamson@redhat.com>
prev parent reply other threads:[~2023-06-28 21:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 7:31 [PATCH v2 0/2] vfio/migration: Make VFIO migration non-experimental Avihai Horon
2023-06-28 7:31 ` [PATCH v2 1/2] vfio/migration: Reset bytes_transferred properly Avihai Horon
2023-06-28 12:50 ` Cédric Le Goater
2023-06-28 7:31 ` [PATCH v2 2/2] vfio/migration: Make VFIO migration non-experimental Avihai Horon
2023-06-28 12:54 ` Cédric Le Goater
2023-06-28 14:51 ` Joao Martins
2023-06-28 16:03 ` Cédric Le Goater
2023-06-29 1:57 ` Duan, Zhenzhong
2023-06-28 15:17 ` Joao Martins
2023-06-28 21:14 ` Alex Williamson [this message]
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=20230628151415.77ee583e.alex.williamson@redhat.com \
--to=alex.williamson@redhat.com \
--cc=avihaih@nvidia.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).