diff options
| author | Peter Xu | 2018-05-02 12:47:28 +0200 |
|---|---|---|
| committer | Juan Quintela | 2018-05-15 20:56:51 +0200 |
| commit | a335debb35bb30ade46e0e62c0b2fbb3882c8448 (patch) | |
| tree | fd354704a9547f76c0ae2ce78f2c966a7904b245 /scripts | |
| parent | migration: new cmd MIG_CMD_RECV_BITMAP (diff) | |
| download | qemu-a335debb35bb30ade46e0e62c0b2fbb3882c8448.tar.gz qemu-a335debb35bb30ade46e0e62c0b2fbb3882c8448.tar.xz qemu-a335debb35bb30ade46e0e62c0b2fbb3882c8448.zip | |
migration: new message MIG_RP_MSG_RECV_BITMAP
Introducing new return path message MIG_RP_MSG_RECV_BITMAP to send
received bitmap of ramblock back to source.
This is the reply message of MIG_CMD_RECV_BITMAP, it contains not only
the header (including the ramblock name), and it was appended with the
whole ramblock received bitmap on the destination side.
When the source receives such a reply message (MIG_RP_MSG_RECV_BITMAP),
it parses it, convert it to the dirty bitmap by inverting the bits.
One thing to mention is that, when we send the recv bitmap, we are doing
these things in extra:
- converting the bitmap to little endian, to support when hosts are
using different endianess on src/dst.
- do proper alignment for 8 bytes, to support when hosts are using
different word size (32/64 bits) on src/dst.
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Message-Id: <20180502104740.12123-13-peterx@redhat.com>
Signed-off-by: Juan Quintela <quintela@redhat.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions