diff options
author | Dr. David Alan Gilbert <dgilbert@redhat.com> | 2019-02-27 13:24:08 +0000 |
---|---|---|
committer | Jason Wang <jasowang@redhat.com> | 2019-03-05 11:27:41 +0800 |
commit | 7659505c1680643d13ad7675f9e649d388303059 (patch) | |
tree | 502da4c1b4ba4b5397727810385c2fe8ca6eb4ad /migration/migration.c | |
parent | 9d8c6a258c70d8ff494489140a4fcb3a965909b2 (diff) |
migration: Switch to using announce timer
Switch the announcements to using the new announce timer.
Move the code that does it to announce.c rather than savevm
because it really has nothing to do with the actual migration.
Migration starts the announce from bh's and so they're all
in the main thread/bql, and so there's never any racing with
the timers themselves.
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
Diffstat (limited to 'migration/migration.c')
-rw-r--r-- | migration/migration.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/migration/migration.c b/migration/migration.c index ca9c35a5cd..c39d3054ec 100644 --- a/migration/migration.c +++ b/migration/migration.c @@ -374,7 +374,7 @@ static void process_incoming_migration_bh(void *opaque) * This must happen after all error conditions are dealt with and * we're sure the VM is going to be running on this host. */ - qemu_announce_self(); + qemu_announce_self(&mis->announce_timer, migrate_announce_params()); if (multifd_load_cleanup(&local_err) != 0) { error_report_err(local_err); |