diff options
| author | David Hildenbrand <david@redhat.com> | 2023-07-06 09:56:08 +0200 |
|---|---|---|
| committer | David Hildenbrand <david@redhat.com> | 2023-07-12 09:25:37 +0200 |
| commit | f161c88a03c646ee308653d3ea99318901093309 (patch) | |
| tree | 469380865b705858918cc39b9592cccefc0b2a0e /migration/postcopy-ram.c | |
| parent | 836f657b6a32baf5579c6f218c9c104363562bb6 (diff) | |
| download | qemu-f161c88a03c646ee308653d3ea99318901093309.zip qemu-f161c88a03c646ee308653d3ea99318901093309.tar.gz qemu-f161c88a03c646ee308653d3ea99318901093309.tar.bz2 | |
migration/ram: Expose ramblock_is_ignored() as migrate_ram_is_ignored()
virtio-mem wants to know whether it should not mess with the RAMBlock
content (e.g., discard RAM, preallocate memory) on incoming migration.
So let's expose that function as migrate_ram_is_ignored() in
migration/misc.h
Message-ID: <20230706075612.67404-4-david@redhat.com>
Acked-by: Peter Xu <peterx@redhat.com>
Tested-by: Mario Casquero <mcasquer@redhat.com>
Reviewed-by: Juan Quintela <quintela@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: David Hildenbrand <david@redhat.com>
Diffstat (limited to 'migration/postcopy-ram.c')
| -rw-r--r-- | migration/postcopy-ram.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/migration/postcopy-ram.c b/migration/postcopy-ram.c index 5615ec2..29aea94 100644 --- a/migration/postcopy-ram.c +++ b/migration/postcopy-ram.c @@ -408,7 +408,7 @@ bool postcopy_ram_supported_by_host(MigrationIncomingState *mis, Error **errp) /* * We don't support postcopy with some type of ramblocks. * - * NOTE: we explicitly ignored ramblock_is_ignored() instead we checked + * NOTE: we explicitly ignored migrate_ram_is_ignored() instead we checked * all possible ramblocks. This is because this function can be called * when creating the migration object, during the phase RAM_MIGRATABLE * is not even properly set for all the ramblocks. |