From: "Cédric Le Goater" <clg@redhat.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Joao Martins <joao.m.martins@oracle.com>,
Avihai Horon <avihaih@nvidia.com>,
Alex Williamson <alex.williamson@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>,
Maor Gottlieb <maorg@nvidia.com>,
Kirti Wankhede <kwankhede@nvidia.com>,
Tarun Gupta <targupta@nvidia.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH 3/3] vfio/migration: Make VFIO migration non-experimental
Date: Mon, 26 Jun 2023 18:39:16 +0200 [thread overview]
Message-ID: <22784bf5-b4bf-2fb7-985c-dfd69899ed1d@redhat.com> (raw)
In-Reply-To: <ZJm6mqJeYS7qMAWR@nvidia.com>
On 6/26/23 18:19, Jason Gunthorpe wrote:
> On Mon, Jun 26, 2023 at 05:26:42PM +0200, Cédric Le Goater wrote:
>
>> Since dirty tracking is a must-have to implement migration support
>> for any existing and future VFIO PCI variant driver, anything else
>> would be experimental code and we are trying to remove the flag !
>> Please correct me if I am wrong.
>
> I don't think we should call it experimental - it is like other qemu
> options where we can choose to run qemu in a suboptimal way.
In that case, whether the driver implements dirty tracking or not
is not a condition to enable migration, only the host kernel driver
support is.
C.
next prev parent reply other threads:[~2023-06-26 16:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 8:23 [PATCH 0/3] vfio/migration: Make VFIO migration non-experimental Avihai Horon
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 [this message]
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=22784bf5-b4bf-2fb7-985c-dfd69899ed1d@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=avihaih@nvidia.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).