qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Tarun Gupta <targupta@nvidia.com>
Cc: kevin.tian@intel.com, cjia@nvidia.com, quintela@redhat.com,
	cohuck@redhat.com, qemu-devel@nongnu.org,
	Kirti Wankhede <kwankhede@nvidia.com>,
	dgilbert@redhat.com, lushenming@huawei.com,
	alex.williamson@redhat.com, dnigam@nvidia.com,
	yan.y.zhao@intel.com, philmd@redhat.com
Subject: Re: [PATCH v2 1/1] docs/devel: Add VFIO device migration documentation
Date: Thu, 11 Mar 2021 09:40:42 +0000	[thread overview]
Message-ID: <YEnlmqNuvIxAB9mc@redhat.com> (raw)
In-Reply-To: <20210310192009.53848-1-targupta@nvidia.com>

On Thu, Mar 11, 2021 at 12:50:09AM +0530, Tarun Gupta wrote:
> Document interfaces used for VFIO device migration. Added flow of state changes
> during live migration with VFIO device. Tested by building docs with the new
> vfio-migration.rst file.
> 
> v2:
> - Included the new vfio-migration.rst file in index.rst
> - Updated dirty page tracking section, also added details about
>   'pre-copy-dirty-page-tracking' opt-out option.
> - Incorporated comments around wording of doc.
> 
> Signed-off-by: Tarun Gupta <targupta@nvidia.com>
> Signed-off-by: Kirti Wankhede <kwankhede@nvidia.com>
> ---
>  MAINTAINERS                   |   1 +
>  docs/devel/index.rst          |   1 +
>  docs/devel/vfio-migration.rst | 135 ++++++++++++++++++++++++++++++++++
>  3 files changed, 137 insertions(+)
>  create mode 100644 docs/devel/vfio-migration.rst


> +Postcopy
> +========
> +
> +Postcopy migration is not supported for VFIO devices.

What is the problem here and is there any plan for how to address it ?

Postcopy is essentially the only migration mechanism that can reliably
complete, so it really should be considered the default approach to
migration for all mgmt apps wanting to do migration, except in special
cases.   IOW, if we want VFIO migration to be viable, we need postcopy
support.


Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|



  reply	other threads:[~2021-03-11  9:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-10 19:20 [PATCH v2 1/1] docs/devel: Add VFIO device migration documentation Tarun Gupta
2021-03-11  9:40 ` Daniel P. Berrangé [this message]
2021-03-11 19:41   ` Dr. David Alan Gilbert
2021-03-12  2:30     ` Tian, Kevin
2021-03-16 15:46       ` Dr. David Alan Gilbert
2021-03-17  1:44         ` Tian, Kevin
2021-03-12  3:13 ` Tian, Kevin
2021-03-16 13:34   ` Tarun Gupta (SW-GPU)
2021-03-17  1:51     ` Tian, Kevin
2021-03-15 17:22 ` Cornelia Huck
2021-03-16 16:18   ` Tarun Gupta (SW-GPU)
2021-03-18 12:28     ` Cornelia Huck

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=YEnlmqNuvIxAB9mc@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=cjia@nvidia.com \
    --cc=cohuck@redhat.com \
    --cc=dgilbert@redhat.com \
    --cc=dnigam@nvidia.com \
    --cc=kevin.tian@intel.com \
    --cc=kwankhede@nvidia.com \
    --cc=lushenming@huawei.com \
    --cc=philmd@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.com \
    --cc=targupta@nvidia.com \
    --cc=yan.y.zhao@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).