On Mon, Jul 17, 2017 at 02:52:31PM -0300, Eduardo Habkost wrote: > On Mon, Jul 17, 2017 at 04:26:03PM +0800, Peter Xu wrote: > > Do the same thing to migration capabilities, just like what we did in > > previous patch for migration parameters. > > > > Signed-off-by: Peter Xu <pet...@redhat.com> > > --- > > migration/migration.c | 17 +++++++++++++++++ > > 1 file changed, 17 insertions(+) > > > > diff --git a/migration/migration.c b/migration/migration.c > > index ad2505c..3208162 100644 > > --- a/migration/migration.c > > +++ b/migration/migration.c > > @@ -2001,6 +2001,9 @@ void migration_global_dump(Monitor *mon) > > ms->send_configuration, ms->send_section_footer); > > } > > > > +#define DEFINE_PROP_MIG_CAP(name, x) \ > > + DEFINE_PROP_BOOL(name, MigrationState, enabled_capabilities[x], false) > > + > > Maybe for the future: have you considered replacing the > enabled_capabilities array with a uint32_t and using > DEFINE_PROP_BIT?
Yes, this sounds reasonable. Noted. > > Reviewed-by: Eduardo Habkost <ehabk...@redhat.com> Thanks! -- Peter Xu
