From: Juan Quintela <quintela@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org, "Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3 2/4] migration: move income process out of multifd
Date: Wed, 27 Jun 2018 15:59:15 +0200 [thread overview]
Message-ID: <87bmbwjpos.fsf@secure.laptop> (raw)
In-Reply-To: <20180627132246.5576-3-peterx@redhat.com> (Peter Xu's message of "Wed, 27 Jun 2018 21:22:44 +0800")
Peter Xu <peterx@redhat.com> wrote:
> Move the call to migration_incoming_process() out of multifd code. It's
> a bit strange that we can migration generic calls in multifd code.
> Instead, let multifd_recv_new_channel() return a boolean showing whether
> it's ready to continue the incoming migration.
>
> Signed-off-by: Peter Xu <peterx@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
next prev parent reply other threads:[~2018-06-27 13:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 13:22 [Qemu-devel] [PATCH v3 0/4] migation: unbreak postcopy recovery Peter Xu
2018-06-27 13:22 ` [Qemu-devel] [PATCH v3 1/4] migration: delay postcopy paused state Peter Xu
2018-06-27 13:22 ` [Qemu-devel] [PATCH v3 2/4] migration: move income process out of multifd Peter Xu
2018-06-27 13:59 ` Juan Quintela [this message]
2018-06-27 13:22 ` [Qemu-devel] [PATCH v3 3/4] migration: unbreak postcopy recovery Peter Xu
2018-06-27 14:00 ` Juan Quintela
2018-06-27 13:22 ` [Qemu-devel] [PATCH v3 4/4] migration: unify incoming processing Peter Xu
2018-06-27 14:01 ` Juan Quintela
2018-07-02 8:04 ` [Qemu-devel] [PATCH v3 0/4] migation: unbreak postcopy recovery Balamuruhan S
2018-07-02 8:46 ` Peter Xu
2018-07-02 9:42 ` Balamuruhan S
2018-07-02 10:18 ` Peter Xu
2018-07-06 8:47 ` Dr. David Alan Gilbert
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=87bmbwjpos.fsf@secure.laptop \
--to=quintela@redhat.com \
--cc=dgilbert@redhat.com \
--cc=peterx@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.