From: Peter Xu <peterx@redhat.com>
To: Yury Kotov <yury-kotov@yandex-team.ru>
Cc: Laurent Vivier <lvivier@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Juan Quintela <quintela@redhat.com>,
"open list:All patches CC here" <qemu-devel@nongnu.org>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
yc-core@yandex-team.ru, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] Deferred incoming migration through fd
Date: Wed, 29 May 2019 11:30:21 +0800 [thread overview]
Message-ID: <20190529033021.GF22773@xz-x1> (raw)
In-Reply-To: <20190528091633.12246-1-yury-kotov@yandex-team.ru>
On Tue, May 28, 2019 at 12:16:31PM +0300, Yury Kotov wrote:
> Hi,
>
> V2:
> * Revert odd changes in migrate()
> * Add short description for socket_send_fds()
> and remove ifdef WIN32 as it's not needed
>
> This series is a continuation of the previous two:
> * migration: Fix handling fd protocol
> * Add 'inline-fd:' protocol for migration
>
> It's about such use case:
> 1. Target VM: exec ...,-incoming defer
> 2. Target VM: getfd("fd-mig")
> 3. Target VM: migrate-incoming("fd:"fd-mig")
> 4. Source VM: getfd("fd-mig")
> 5. Source VM: migrate("fd-mig")
>
> Currently, it's not possible to do the step 3, because for incoming migration
> "fd:" protocol expects an integer, not the name of fd.
Reviewed-by: Peter Xu <peterx@redhat.com>
I gave a quick shot on the new test - it runs well.
--
Peter Xu
prev parent reply other threads:[~2019-05-29 3:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 9:16 [Qemu-devel] [PATCH v2 0/2] Deferred incoming migration through fd Yury Kotov
2019-05-28 9:16 ` [Qemu-devel] [PATCH v2 1/2] migration: Fix fd protocol for incoming defer Yury Kotov
2019-05-28 9:16 ` [Qemu-devel] [PATCH v2 2/2] migration-test: Add a test for fd protocol Yury Kotov
2019-05-29 3:30 ` Peter Xu [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=20190529033021.GF22773@xz-x1 \
--to=peterx@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=thuth@redhat.com \
--cc=yc-core@yandex-team.ru \
--cc=yury-kotov@yandex-team.ru \
/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).