On Tue, Apr 7, 2015 at 3:11 PM, Stefan Hajnoczi stefa...@redhat.com wrote:
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
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
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
On 04/03/2015 01:50 AM, 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
On Thu, Apr 02, 2015 at 08:53:04PM +0200, Paolo Bonzini wrote:
On 02/04/2015 20:46, Michael S. Tsirkin wrote:
Oh, true in fact. It might be a good idea to add something like this to
the commit log:
Additionally, virtio spec requires that device writes at least
len bytes to
On Thu, Apr 02, 2015 at 07:57:22PM +0200, Paolo Bonzini wrote:
On 02/04/2015 19:54, Michael S. Tsirkin wrote:
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
On 02/04/2015 19:54, Michael S. Tsirkin wrote:
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
On 02/04/2015 20:46, Michael S. Tsirkin wrote:
Oh, true in fact. It might be a good idea to add something like this to
the commit log:
Additionally, virtio spec requires that device writes at least
len bytes to descriptor - so that driver can rely on
bytes 0..len-1
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
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
10 matches
Mail list logo
