From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>,
Changpeng Liu <changpeng.liu@intel.com>,
Laurent Vivier <lvivier@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org,
Max Reitz <mreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
virtio-comment@lists.oasis-open.org
Subject: Re: [Qemu-devel] [PATCH RFC 2/2] tests/virtio-blk: add test for WRITE_ZEROES command
Date: Sun, 27 Jan 2019 12:57:20 +0000 [thread overview]
Message-ID: <20190127125720.GC13784@stefanha-x1.localdomain> (raw)
In-Reply-To: <20190125141502-mutt-send-email-mst@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
On Fri, Jan 25, 2019 at 02:17:01PM -0500, Michael S. Tsirkin wrote:
> On Fri, Jan 25, 2019 at 03:12:45PM +0000, Stefan Hajnoczi wrote:
> > Based on the Linux guest driver code and the lack of more evidence in
> > the spec, I'm pretty sure data[] doesn't need to be padded to 512 bytes
> > for discard/write zero requests.
>
> OK. Must devices support such padding?
I see no reason to require padding. Host APIs and physical storage
controllers do not require it.
> > > Looking at the QEMU sources, it seems like it can deal with both and
> > > always sets the status right behind the last byte:
> > >
> > > req->in = (void *)in_iov[in_num - 1].iov_base
> > > + in_iov[in_num - 1].iov_len
> > > - sizeof(struct virtio_blk_inhdr);
> > >
> > > Anyway, I think the virtio spec should be clearer here to avoid bad
> > > implementations in the future, so maybe Changpeng or Michael could
> > > update the spec here a little bit?
> >
> > Yep, good point. VIRTIO 1.1 is available for public comments, so I've
> > CCed the list.
> >
> > Stefan
>
> Thanks!
> Care creating a github issue? And maybe proposing a spec patch.
Okay. I will do this on Wednesday 30th of January.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2019-01-27 12:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 17:23 [Qemu-devel] [PATCH RFC 0/2] virtio-blk: add DISCARD and WRITE ZEROES features Stefano Garzarella
2019-01-24 17:23 ` [Qemu-devel] [PATCH RFC 1/2] " Stefano Garzarella
2019-01-24 17:55 ` Dr. David Alan Gilbert
2019-01-24 18:31 ` Stefano Garzarella
2019-01-25 14:58 ` Stefan Hajnoczi
2019-01-25 16:18 ` Stefano Garzarella
2019-01-27 12:51 ` Stefan Hajnoczi
2019-01-28 8:28 ` Stefano Garzarella
2019-01-24 17:23 ` [Qemu-devel] [PATCH RFC 2/2] tests/virtio-blk: add test for WRITE_ZEROES command Stefano Garzarella
2019-01-25 6:01 ` Thomas Huth
2019-01-25 6:07 ` Thomas Huth
2019-01-25 6:07 ` Thomas Huth
2019-01-25 8:16 ` Stefano Garzarella
2019-01-25 8:49 ` Thomas Huth
2019-01-25 11:58 ` Liu, Changpeng
2019-01-25 12:48 ` Thomas Huth
2019-01-25 19:18 ` Michael S. Tsirkin
2019-01-25 15:12 ` Stefan Hajnoczi
2019-01-25 19:17 ` Michael S. Tsirkin
2019-01-27 12:57 ` Stefan Hajnoczi [this message]
2019-01-27 18:42 ` Michael S. Tsirkin
2019-01-30 7:39 ` Stefan Hajnoczi
2019-01-30 7:59 ` Liu, Changpeng
2019-01-25 19:14 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190127125720.GC13784@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=changpeng.liu@intel.com \
--cc=kwolf@redhat.com \
--cc=lvivier@redhat.com \
--cc=mreitz@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=thuth@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).