From: Cornelia Huck <cohuck@redhat.com>
To: Tarun Gupta <targupta@nvidia.com>
Cc: kevin.tian@intel.com, cjia@nvidia.com, quintela@redhat.com,
alex.williamson@redhat.com, qemu-devel@nongnu.org,
yan.y.zhao@intel.com, lushenming@huawei.com,
kwankhede@nvidia.com, dnigam@nvidia.com, berrange@redhat.com,
philmd@redhat.com, dgilbert@redhat.com
Subject: Re: [PATCH v4 1/1] docs/devel: Add VFIO device migration documentation
Date: Mon, 12 Apr 2021 12:10:22 +0200 [thread overview]
Message-ID: <20210412121022.48a66e07.cohuck@redhat.com> (raw)
In-Reply-To: <20210409134346.16490-1-targupta@nvidia.com>
On Fri, 9 Apr 2021 19:13:46 +0530
Tarun Gupta <targupta@nvidia.com> wrote:
> Document interfaces used for VFIO device migration. Added flow of state changes
> during live migration with VFIO device.
>
> Co-developed-by: Kirti Wankhede <kwankhede@nvidia.com>
This still needs Kirti's S-o-b as well (i.e. both tags need to be
paired.)
> Signed-off-by: Tarun Gupta <targupta@nvidia.com>
> ---
> Tested by building docs with new vfio-migration.rst file
>
> v4:
> - Added info about vfio_listener_log_global_[start|stop]
> - Added info about `save_state` callback.
> - Incorporated comments from v3.
>
> v3:
> - Add introductory line about VM migration in general.
> - Remove occurcences of vfio_pin_pages() to describe pinning.
> - Incorporated comments from v2
>
> 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.
>
The change log and the other extra information also need to be followed
by another '---'.
> MAINTAINERS | 1 +
> docs/devel/index.rst | 1 +
> docs/devel/vfio-migration.rst | 150 ++++++++++++++++++++++++++++++++++
> 3 files changed, 152 insertions(+)
> create mode 100644 docs/devel/vfio-migration.rst
Aside from the meta issues above, the patch looks good to me.
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
prev parent reply other threads:[~2021-04-12 10:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 13:43 [PATCH v4 1/1] docs/devel: Add VFIO device migration documentation Tarun Gupta
2021-04-12 10:10 ` Cornelia Huck [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=20210412121022.48a66e07.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=berrange@redhat.com \
--cc=cjia@nvidia.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).