qemu-e2k/hw/block
Paolo Bonzini 2a6cdd6d35 virtio-blk: correctly dirty guest memory
After qemu_iovec_destroy, the QEMUIOVector's size is zeroed and
the zero size ultimately is used to compute virtqueue_push's len
argument.  Therefore, reads from virtio-blk devices did not
migrate their results correctly.  (Writes were okay).

Save the size in virtio_blk_handle_request, and use it when the request
is completed.

Based on a patch by Wen Congyang.

Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Tested-by: Li Zhijian <lizhijian@cn.fujitsu.com>
Message-id: 1427997044-392-1-git-send-email-pbonzini@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
2015-04-08 10:39:18 +01:00
..
dataplane virtio-blk: correctly dirty guest memory 2015-04-08 10:39:18 +01:00
block.c
cdrom.c
ecc.c
fdc.c
hd-geometry.c
m25p80.c hw: Mark devices picking up block backends actively FIXME 2015-04-02 15:26:27 +02:00
Makefile.objs
nand.c
nvme.c nvme: Fix unintentional integer overflow (OVERFLOW_BEFORE_WIDEN) 2015-03-27 10:01:12 +00:00
nvme.h
onenand.c
pflash_cfi01.c
pflash_cfi02.c
tc58128.c
virtio-blk.c virtio-blk: correctly dirty guest memory 2015-04-08 10:39:18 +01:00
xen_blkif.h
xen_disk.c