[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v2 for-2.3] virtio-blk: correctly dirty guest me
From: |
Stefan Hajnoczi |
Subject: |
Re: [Qemu-devel] [PATCH v2 for-2.3] virtio-blk: correctly dirty guest memory |
Date: |
Wed, 8 Apr 2015 10:42:59 +0100 |
User-agent: |
Mutt/1.5.23 (2014-03-12) |
On Thu, Apr 02, 2015 at 07:50:44PM +0200, Paolo Bonzini wrote:
> 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 <address@hidden>
> Signed-off-by: Paolo Bonzini <address@hidden>
> ---
> hw/block/dataplane/virtio-blk.c | 3 +--
> hw/block/virtio-blk.c | 13 ++++++++++++-
Applied to my block tree for QEMU 2.3-rc3:
https://github.com/stefanha/qemu/commits/block
I can still drop it if there is an objection, so just let me know.
Several related points have been mentioned but they are orthogonal and
less urgent. Please address them in separate QEMU 2.4 patches.
Stefan
pgpzqlkwJRnod.pgp
Description: PGP signature
Re: [Qemu-devel] [PATCH v2 for-2.3] virtio-blk: correctly dirty guest memory, Li Zhijian, 2015/04/03
Re: [Qemu-devel] [PATCH v2 for-2.3] virtio-blk: correctly dirty guest memory, Stefan Hajnoczi, 2015/04/07
Re: [Qemu-devel] [PATCH v2 for-2.3] virtio-blk: correctly dirty guest memory,
Stefan Hajnoczi <=