From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org
Cc: fam@euphon.net, kwolf@redhat.com, ehabkost@redhat.com,
qemu-devel@nongnu.org, mreitz@redhat.com, stefanha@redhat.com,
crosa@redhat.com, den@openvz.org
Subject: Re: [PATCH v8 6/7] block: drop bdrv_prwv
Date: Thu, 24 Sep 2020 10:31:20 +0200 [thread overview]
Message-ID: <e3550d8b-6a08-1c38-1804-d5fd533fb13c@redhat.com> (raw)
In-Reply-To: <20200915164411.20590-7-vsementsov@virtuozzo.com>
On 9/15/20 6:44 PM, Vladimir Sementsov-Ogievskiy wrote:
> Now that we are not maintaining boilerplate code for coroutine
> wrappers, there is no more sense in keeping the extra indirection layer
> of bdrv_prwv(). Let's drop it and instead generate pure bdrv_preadv()
> and bdrv_pwritev().
>
> Currently, bdrv_pwritev() and bdrv_preadv() are returning bytes on
> success, auto generated functions will instead return zero, as their
> _co_ prototype. Still, it's simple to make the conversion safe: the
> only external user of bdrv_pwritev() is test-bdrv-drain, and it is
> comfortable enough with bdrv_co_pwritev() instead. So prototypes are
> moved to local block/coroutines.h. Next, the only internal use is
> bdrv_pread() and bdrv_pwrite(), which are modified to return bytes on
> success.
>
> Of course, it would be great to convert bdrv_pread() and bdrv_pwrite()
> to return 0 on success. But this requires audit (and probably
> conversion) of all their users, let's leave it for another day
> refactoring.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> ---
> block/coroutines.h | 10 ++++-----
> include/block/block.h | 2 --
> block/io.c | 49 ++++++++---------------------------------
> tests/test-bdrv-drain.c | 2 +-
> 4 files changed, 15 insertions(+), 48 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
next prev parent reply other threads:[~2020-09-24 8:33 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 16:44 [PATCH v8 0/7] coroutines: generate wrapper code Vladimir Sementsov-Ogievskiy
2020-09-15 16:44 ` [PATCH v8 1/7] block: return error-code from bdrv_invalidate_cache Vladimir Sementsov-Ogievskiy
2020-09-24 8:26 ` Philippe Mathieu-Daudé
2020-09-24 11:19 ` Stefan Hajnoczi
2020-09-15 16:44 ` [PATCH v8 2/7] block/io: refactor coroutine wrappers Vladimir Sementsov-Ogievskiy
2020-09-23 19:41 ` Eric Blake
2020-09-24 8:27 ` Philippe Mathieu-Daudé
2020-09-24 11:24 ` Stefan Hajnoczi
2020-09-15 16:44 ` [PATCH v8 3/7] block: declare some coroutine functions in block/coroutines.h Vladimir Sementsov-Ogievskiy
2020-09-23 21:47 ` Eric Blake
2020-09-24 8:34 ` Philippe Mathieu-Daudé
2020-09-24 11:25 ` Stefan Hajnoczi
2020-09-15 16:44 ` [PATCH v8 4/7] scripts: add block-coroutine-wrapper.py Vladimir Sementsov-Ogievskiy
2020-09-15 20:02 ` Vladimir Sementsov-Ogievskiy
2020-09-24 0:00 ` Eric Blake
2020-09-24 1:20 ` Eric Blake
2020-09-24 7:08 ` Vladimir Sementsov-Ogievskiy
2020-09-24 6:59 ` Vladimir Sementsov-Ogievskiy
2020-09-24 16:20 ` John Snow
2020-09-24 0:18 ` Eric Blake
2020-09-24 7:08 ` Vladimir Sementsov-Ogievskiy
2020-09-24 11:40 ` Stefan Hajnoczi
2020-09-24 17:56 ` Eric Blake
2020-09-24 18:52 ` Vladimir Sementsov-Ogievskiy
2020-09-15 16:44 ` [PATCH v8 5/7] block: generate coroutine-wrapper code Vladimir Sementsov-Ogievskiy
2020-09-24 12:14 ` Stefan Hajnoczi
2020-09-15 16:44 ` [PATCH v8 6/7] block: drop bdrv_prwv Vladimir Sementsov-Ogievskiy
2020-09-24 8:31 ` Philippe Mathieu-Daudé [this message]
2020-09-24 12:15 ` Stefan Hajnoczi
2020-09-15 16:44 ` [PATCH v8 7/7] block/io: refactor save/load vmstate Vladimir Sementsov-Ogievskiy
2020-09-23 20:10 ` Eric Blake
2020-09-24 7:20 ` Vladimir Sementsov-Ogievskiy
2020-09-24 12:16 ` Stefan Hajnoczi
2020-09-24 12:16 ` [PATCH v8 0/7] coroutines: generate wrapper code Stefan Hajnoczi
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=e3550d8b-6a08-1c38-1804-d5fd533fb13c@redhat.com \
--to=philmd@redhat.com \
--cc=crosa@redhat.com \
--cc=den@openvz.org \
--cc=ehabkost@redhat.com \
--cc=fam@euphon.net \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--cc=vsementsov@virtuozzo.com \
/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).