Juan Quintela ddac5cb2d9 multifd: Be consistent about using uint64_t ...

We transmit ram_addr_t always as uint64_t.  Be consistent in its
use (on 64bit system, it is always uint64_t problem is 32bits).

Signed-off-by: Juan Quintela <quintela@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
Reviewed-by: Dr. David Alan Gilbert <dgilbert@redhat.com>

2020-01-20 09:17:07 +01:00

..

block-dirty-bitmap.c

…

block.c

…

block.h

…

channel.c

…

channel.h

…

colo-failover.c

…

colo.c

…

exec.c

…

exec.h

…

fd.c

…

fd.h

…

global_state.c

…

Makefile.objs

…

migration.c

…

migration.h

…

page_cache.c

…

page_cache.h

…

postcopy-ram.c

…

postcopy-ram.h

…

qemu-file-channel.c

…

qemu-file-channel.h

…

qemu-file.c

…

qemu-file.h

…

qjson.c

…

qjson.h

…

ram.c

multifd: Be consistent about using uint64_t

2020-01-20 09:17:07 +01:00

ram.h

…

rdma.c

…

rdma.h

…

savevm.c

…

savevm.h

…

socket.c

…

socket.h

…

tls.c

…

tls.h

…

trace-events

…

vmstate-types.c

…

vmstate.c

…

xbzrle.c

…

xbzrle.h

…