From: Peter Maydell <peter.maydell@linaro.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Kirti Wankhede <kwankhede@nvidia.com>,
Cornelia Huck <cohuck@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PULL 0/2] VFIO updates for QEMU 5.2-rc3
Date: Mon, 23 Nov 2020 22:37:52 +0000 [thread overview]
Message-ID: <CAFEAcA8CeGB=Xom=adn9rK5FNymbTYFR_XRVBOaiC1_2ejYuog@mail.gmail.com> (raw)
In-Reply-To: <160615410107.26810.2586812803373008210.stgit@gimli.home>
On Mon, 23 Nov 2020 at 17:59, Alex Williamson
<alex.williamson@redhat.com> wrote:
>
> The following changes since commit 683685e72dccaf8cb9fe8ffa20f5c5aacea72118:
>
> Merge remote-tracking branch 'remotes/stefanha-gitlab/tags/block-pull-request' into staging (2020-11-23 13:03:13 +0000)
>
> are available in the Git repository at:
>
> git://github.com/awilliam/qemu-vfio.git tags/vfio-update-20201123.0
>
> for you to fetch changes up to bb0990d1740f6dced5b50a923677034c9399c213:
>
> vfio: Change default dirty pages tracking behavior during migration (2020-11-23 10:05:58 -0700)
>
> ----------------------------------------------------------------
> VFIO update 2020-11-23
>
> * Enable pre-copy dirty page tracking by default (Kirti Wankhede)
>
> * Mark migration as experimental (Alex Williamson)
>
> ----------------------------------------------------------------
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/5.2
for any user-visible changes.
-- PMM
prev parent reply other threads:[~2020-11-23 22:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 17:56 [PULL 0/2] VFIO updates for QEMU 5.2-rc3 Alex Williamson
2020-11-23 17:56 ` [PULL 1/2] vfio: Make migration support experimental Alex Williamson
2020-11-23 17:57 ` [PULL 2/2] vfio: Change default dirty pages tracking behavior during migration Alex Williamson
2020-11-23 22:37 ` Peter Maydell [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='CAFEAcA8CeGB=Xom=adn9rK5FNymbTYFR_XRVBOaiC1_2ejYuog@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kwankhede@nvidia.com \
--cc=qemu-devel@nongnu.org \
/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).