[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 15/20] migration: Allow migrate-recover to run multiple times
From: |
Peter Xu |
Subject: |
Re: [PATCH 15/20] migration: Allow migrate-recover to run multiple times |
Date: |
Tue, 22 Feb 2022 10:51:00 +0800 |
On Mon, Feb 21, 2022 at 05:03:24PM +0000, Dr. David Alan Gilbert wrote:
> * Peter Xu (peterx@redhat.com) wrote:
> > Previously migration didn't have an easy way to cleanup the listening
> > transport, migrate recovery only allows to execute once. That's done with a
> > trick flag in postcopy_recover_triggered.
> >
> > Now the facility is already there.
> >
> > Drop postcopy_recover_triggered and instead allows a new migrate-recover to
> > release the previous listener transport.
> >
> > Signed-off-by: Peter Xu <peterx@redhat.com>
>
> OK, was that the only reason you couldn't recover twice?
We could recover twice, but we couldn't specify the listening port twice
because AFAIU previously we don't have a good way to clean the existing
listener.
IOW we could always run pause->recover->pause->recover sequence even before
this patch[set], but we can never run continuous recover->recover because
the 2nd one will fail telling that we've already setup a recovery port.
>
>
> Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Thanks!
--
Peter Xu
- Re: [PATCH 12/20] migration: Export ram_load_postcopy(), (continued)
[PATCH 14/20] migration: Add migration_incoming_transport_cleanup(), Peter Xu, 2022/02/16
[PATCH 15/20] migration: Allow migrate-recover to run multiple times, Peter Xu, 2022/02/16
[PATCH 16/20] migration: Add postcopy-preempt capability, Peter Xu, 2022/02/16
[PATCH 17/20] migration: Postcopy preemption preparation on channel creation, Peter Xu, 2022/02/16
[PATCH 18/20] migration: Postcopy preemption enablement, Peter Xu, 2022/02/16