From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Juan Quintela <quintela@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
peterx@redhat.com
Subject: [Qemu-devel] [PATCH v2 3/5] migration: do explicit incoming setup for rdma
Date: Wed, 27 Jun 2018 18:51:10 +0800 [thread overview]
Message-ID: <20180627105112.31401-4-peterx@redhat.com> (raw)
In-Reply-To: <20180627105112.31401-1-peterx@redhat.com>
RDMA does not support postcopy recovery, so no need to go into such
logic. Instead of calling migration_fd_process_incoming(), let's call
the two functions that setup the incoming migration. There should have
no functional change at all.
Signed-off-by: Peter Xu <peterx@redhat.com>
---
migration/rdma.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/migration/rdma.c b/migration/rdma.c
index 8bd7159059..217cdd7dd8 100644
--- a/migration/rdma.c
+++ b/migration/rdma.c
@@ -3687,7 +3687,8 @@ static void rdma_accept_incoming_migration(void *opaque)
}
rdma->migration_started_on_destination = 1;
- migration_fd_process_incoming(f);
+ migration_incoming_setup(f);
+ migration_incoming_process();
}
void rdma_start_incoming_migration(const char *host_port, Error **errp)
--
2.17.1
next prev parent reply other threads:[~2018-06-27 10:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-27 10:51 [Qemu-devel] [PATCH v2 0/5] migation: unbreak postcopy recovery Peter Xu
2018-06-27 10:51 ` [Qemu-devel] [PATCH v2 1/5] migration: delay postcopy paused state Peter Xu
2018-06-27 10:51 ` [Qemu-devel] [PATCH v2 2/5] migration: move income process out of multifd Peter Xu
2018-06-27 10:51 ` Peter Xu [this message]
2018-06-27 12:25 ` [Qemu-devel] [PATCH v2 3/5] migration: do explicit incoming setup for rdma Dr. David Alan Gilbert
2018-06-27 13:03 ` Peter Xu
2018-06-27 14:13 ` Dr. David Alan Gilbert
2018-06-29 6:58 ` Peter Xu
2018-06-27 10:51 ` [Qemu-devel] [PATCH v2 4/5] migration: unbreak postcopy recovery Peter Xu
2018-06-27 10:51 ` [Qemu-devel] [PATCH v2 5/5] migration: unify incoming processing Peter Xu
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=20180627105112.31401-4-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).