All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
	Maor Lipchuk <mlipchuk@redhat.com>,
	"Daniel P. Berrange" <berrange@redhat.com>,
	Nir Soffer <nsoffer@redhat.com>,
	Alberto Garcia <berto@igalia.com>, John Snow <jsnow@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 1/9] block: add bdrv_measure() API
Date: Thu, 20 Apr 2017 11:49:02 +0100	[thread overview]
Message-ID: <20170420104902.GD28129@stefanha-x1.localdomain> (raw)
In-Reply-To: <8c7093c1-8c10-c36c-3628-421664ca02be@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1110 bytes --]

On Wed, Apr 19, 2017 at 08:32:06AM -0500, Eric Blake wrote:
> On 04/19/2017 08:27 AM, Stefan Hajnoczi wrote:
> 
> >>
> >> I know we haven't done a good job in the past, but should we start
> >> trying to do better at documenting callback constraints of new things
> >> added in this header?
> > 
> > .bdrv_measure() is a 1:1 pass-through of the public bdrv_measure()
> > function.  All the public function does is to dereference
> > drv->bdrv_measure.
> > 
> > I think that's why many of the other callbacks also have no
> > documentation - they inherit semantics from the public function.  We
> > don't need to duplicate the doc comments.
> 
> Sometimes, though, there are slightly different semantics (for example,
> we guarantee that the parameters to the driver code have already been
> validated against image size, properly sliced-and-diced to match block
> limits, and so on), so that the drivers don't have to do as much work.
> Documenting these contract guarantees would be useful.

Fair enough.

> But as I said, it's not something we have to solve in this series.

Okay.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  reply	other threads:[~2017-04-20 10:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 13:57 [Qemu-devel] [PATCH v5 0/9] qemu-img: add measure sub-command Stefan Hajnoczi
2017-04-18 13:57 ` [Qemu-devel] [PATCH v5 1/9] block: add bdrv_measure() API Stefan Hajnoczi
2017-04-18 15:08   ` Eric Blake
2017-04-19 13:27     ` Stefan Hajnoczi
2017-04-19 13:32       ` Eric Blake
2017-04-20 10:49         ` Stefan Hajnoczi [this message]
2017-04-18 13:57 ` [Qemu-devel] [PATCH v5 2/9] raw-format: add bdrv_measure() support Stefan Hajnoczi
2017-04-18 13:57 ` [Qemu-devel] [PATCH v5 3/9] qcow2: extract preallocation calculation function Stefan Hajnoczi
2017-04-18 13:57 ` [Qemu-devel] [PATCH v5 4/9] qcow2: make refcount size calculation conservative Stefan Hajnoczi
2017-05-08 13:15   ` Alberto Garcia
2017-04-18 13:57 ` [Qemu-devel] [PATCH v5 5/9] qcow2: extract image creation option parsing Stefan Hajnoczi
2017-04-18 13:57 ` [Qemu-devel] [PATCH v5 6/9] qcow2: add bdrv_measure() support Stefan Hajnoczi
2017-05-08 13:16   ` Alberto Garcia
2017-04-18 13:57 ` [Qemu-devel] [PATCH v5 7/9] qemu-img: add measure subcommand Stefan Hajnoczi
2017-05-08 14:17   ` Alberto Garcia
2017-04-18 13:57 ` [Qemu-devel] [PATCH v5 8/9] qemu-iotests: support per-format golden output files Stefan Hajnoczi
2017-05-08 13:18   ` Alberto Garcia
2017-04-18 13:57 ` [Qemu-devel] [PATCH v5 9/9] iotests: add test 178 for qemu-img measure Stefan Hajnoczi
2017-05-08 13:18   ` Alberto Garcia

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=20170420104902.GD28129@stefanha-x1.localdomain \
    --to=stefanha@redhat.com \
    --cc=berrange@redhat.com \
    --cc=berto@igalia.com \
    --cc=eblake@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mlipchuk@redhat.com \
    --cc=nsoffer@redhat.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.