On Wed, Jun 27, 2018 at 03:13:04PM +0100, Dr. David Alan Gilbert wrote:
> * Peter Xu (pet...@redhat.com) wrote:
> > On Wed, Jun 27, 2018 at 01:25:45PM +0100, Dr. David Alan Gilbert wrote:
> > > * Peter Xu (pet...@redhat.com) wrote:
> > > > RDMA does not support postcopy recovery, so no need to go i
* Peter Xu (pet...@redhat.com) wrote:
> On Wed, Jun 27, 2018 at 01:25:45PM +0100, Dr. David Alan Gilbert wrote:
> > * Peter Xu (pet...@redhat.com) wrote:
> > > RDMA does not support postcopy recovery, so no need to go into such
> > > logic. Instead of calling migration_fd_process_incoming(), let's
On Wed, Jun 27, 2018 at 01:25:45PM +0100, Dr. David Alan Gilbert wrote:
> * Peter Xu (pet...@redhat.com) wrote:
> > 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 inc
* Peter Xu (pet...@redhat.com) wrote:
> 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.
Can you expl
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
---
migration/rdma.c | 3 ++-
1
