zhanghailiang <zhang.zhanghaili...@huawei.com> wrote: > For migration destination, sometimes we need to know its state, > and it is also useful for tracing migration incoming process. > > Here we add a new member 'state' for MigrationIncomingState, > and also use migrate_set_state() to modify its value. > We fix the first parameter of migrate_set_state(), and make it > public. > > Signed-off-by: zhanghailiang <zhang.zhanghaili...@huawei.com> > Reviewed-by: Dr. David Alan Gilbert <dgilb...@redhat.com>
1st: split the patch about the change in migrate_set_state prototype, and the rest. Once there, if we are going to do this, at least show it on info migrate on destination? If we are going this way, I think it is going to be better to reuse MigrationState? That way, we could make the info migrate statistics easier to understand? Thanks, Juan.
