aboutsummaryrefslogtreecommitdiff
path: root/migration/trace-events
diff options
context:
space:
mode:
authorDr. David Alan Gilbert <dgilbert@redhat.com>2017-02-24 18:28:29 +0000
committerDr. David Alan Gilbert <dgilbert@redhat.com>2017-02-28 11:30:23 +0000
commite8ca1db29b349e780743c504cb735c8e1d542a8c (patch)
treeb917e5911497dfbf56cea84d1e9080ec16d4a1a9 /migration/trace-events
parentf9c8caa04f7f2bed12dc5a4d7e92a59fe6677b37 (diff)
downloadqemu-e8ca1db29b349e780743c504cb735c8e1d542a8c.zip
qemu-e8ca1db29b349e780743c504cb735c8e1d542a8c.tar.gz
qemu-e8ca1db29b349e780743c504cb735c8e1d542a8c.tar.bz2
postcopy: Transmit ram size summary word
Replace the host page-size in the 'advise' command by a pagesize summary bitmap; if the VM is just using normal RAM then this will be exactly the same as before, however if they're using huge pages they'll be different, and thus: a) Migration from/to old qemu's that don't understand huge pages will fail early. b) Migrations with different size RAMBlocks will also fail early. This catches it very early; earlier than the detailed per-block check in the next patch. Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com> Reviewed-by: Laurent Vivier <lvivier@redhat.com> Reviewed-by: Juan Quintela <quintela@redhat.com> Message-Id: <20170224182844.32452-2-dgilbert@redhat.com> Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Diffstat (limited to 'migration/trace-events')
0 files changed, 0 insertions, 0 deletions