migration: Poison ramblock loops in migration
commit343f632c70ab401b1343140c3b19c9fb99395323
authorDr. David Alan Gilbert <dgilbert@redhat.com>
Tue, 5 Jun 2018 16:25:45 +0000 (5 17:25 +0100)
committerDr. David Alan Gilbert <dgilbert@redhat.com>
Fri, 15 Jun 2018 13:40:56 +0000 (15 14:40 +0100)
tree5a6163850c759e3aa46efc0e762e08d52ac5cc9f
parentff0769a4adf52299504642882efba83ca1340a80
migration: Poison ramblock loops in migration

The migration code should be using the
  RAMBLOCK_FOREACH_MIGRATABLE and qemu_ram_foreach_block_migratable
not the all-block versions;  poison them so that we can't accidentally
use them.

Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Message-Id: <20180605162545.80778-3-dgilbert@redhat.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
Reviewed-by: Cédric Le Goater <clg@kaod.org>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
include/exec/ramlist.h
migration/migration.h
migration/ram.c