From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, qemu-block@nongnu.org
Subject: [PATCH v2 0/4] block: clean up coroutine versions of bdrv_{is_allocated, block_status}*
Date: Thu, 1 Jun 2023 13:51:27 +0200 [thread overview]
Message-ID: <20230601115131.196234-1-pbonzini@redhat.com> (raw)
Provide coroutine versions of bdrv_is_allocated* and bdrv_block_status*,
since the underlying BlockDriver API is coroutine-based, and use
automatically-generated wrappers for the "mixed" versions.
Paolo
v1->v2: rename the old bdrv_co_block_status to bdrv_co_do_block_status
Paolo Bonzini (4):
block: rename the bdrv_co_block_status static function
block: complete public block status API
block: switch to co_wrapper for bdrv_is_allocated_*
block: convert more bdrv_is_allocated* and bdrv_block_status* calls to
coroutine versions
block/copy-before-write.c | 2 +-
block/copy-on-read.c | 8 ++--
block/io.c | 96 ++++++++++-----------------------------
block/mirror.c | 10 ++--
block/qcow2.c | 5 +-
block/replication.c | 8 ++--
block/stream.c | 8 ++--
block/vvfat.c | 18 ++++----
include/block/block-io.h | 30 +++++++-----
9 files changed, 73 insertions(+), 112 deletions(-)
--
2.40.1
next reply other threads:[~2023-06-01 11:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-01 11:51 Paolo Bonzini [this message]
2023-06-01 11:51 ` [PATCH v2 1/4] block: rename the bdrv_co_block_status static function Paolo Bonzini
2023-06-01 13:36 ` Eric Blake
2023-06-01 11:51 ` [PATCH v2 2/4] block: complete public block status API Paolo Bonzini
2023-06-01 13:39 ` Eric Blake
2023-06-01 11:51 ` [PATCH v2 3/4] block: switch to co_wrapper for bdrv_is_allocated_* Paolo Bonzini
2023-06-01 11:51 ` [PATCH v2 4/4] block: convert more bdrv_is_allocated* and bdrv_block_status* calls to coroutine versions Paolo Bonzini
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=20230601115131.196234-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--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 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).