migration: let MigrationState be a qdev
commite5cb7e7677010f529d3f0f9dcdb385dea9446f8d
authorPeter Xu <peterx@redhat.com>
Tue, 27 Jun 2017 04:10:13 +0000 (27 12:10 +0800)
committerJuan Quintela <quintela@redhat.com>
Wed, 28 Jun 2017 09:18:38 +0000 (28 11:18 +0200)
tree68da25974b448f88a66b7b876a880de11716534b
parenta0660e0bb8a501525c5bdfc67d56b954c3da664d
migration: let MigrationState be a qdev

Let the old man "MigrationState" join the object family. Direct benefit
is that we can start to use all the property features derived from
current QDev, like: HW_COMPAT_* bits, command line setup for migration
parameters (so will never need to set them up each time using HMP/QMP,
this is really, really attractive for test writters), etc.

I see no reason to disallow this happen yet. So let's start from this
one, to see whether it would be anything good.

Now we init the MigrationState struct statically in main() to make sure
it's initialized after global properties are applied, since we'll use
them during creation of the object.

No functional change at all.

Reviewed-by: Juan Quintela <quintela@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <1498536619-14548-5-git-send-email-peterx@redhat.com>
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
include/migration/misc.h
migration/migration.c
migration/migration.h
vl.c