On Mon, 4 Nov 2024 at 22:23, Peter Xu wrote:
> We definitely need a helper like this to simply detect what the user chose
> on the feature.
>
> You can still introduce a new helper, e.g. migrate_multifd_precopy(), if
> that simplifies the code.
Okay. Thank you.
---
- Prasad
On Mon, Nov 04, 2024 at 05:53:22PM +0530, Prasad Pandit wrote:
> On Fri, 1 Nov 2024 at 20:06, Peter Xu wrote:
> > > -return s->capabilities[MIGRATION_CAPABILITY_MULTIFD];
> > > +return s->capabilities[MIGRATION_CAPABILITY_MULTIFD]
> > > +&& !migration_in_postcopy();
> > > }
>
On Fri, 1 Nov 2024 at 20:06, Peter Xu wrote:
> > -return s->capabilities[MIGRATION_CAPABILITY_MULTIFD];
> > +return s->capabilities[MIGRATION_CAPABILITY_MULTIFD]
> > +&& !migration_in_postcopy();
> > }
>
> We need to keep this as-is.. I'm afraid.
> You can always do proper che
On Tue, Oct 29, 2024 at 08:39:06PM +0530, Prasad Pandit wrote:
> From: Prasad Pandit
>
> Remove multifd capability check with Postcopy mode.
> This helps to enable both multifd and postcopy together.
>
> Update migrate_multifd() to return false when migration
> reaches Postcopy phase. In Postcop
From: Prasad Pandit
Remove multifd capability check with Postcopy mode.
This helps to enable both multifd and postcopy together.
Update migrate_multifd() to return false when migration
reaches Postcopy phase. In Postcopy phase, source guest
is paused, so the migration threads on the source stop
