From: Manos Pitsidianakis <el13635@mail.ntua.gr>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: qemu-block <qemu-block@nongnu.org>, Kevin Wolf <kwolf@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: [Qemu-devel] [PATCH 0/2] block: block driver callbacks fixes
Date: Wed, 28 Jun 2017 01:46:14 +0300 [thread overview]
Message-ID: <20170627224616.18538-1-el13635@mail.ntua.gr> (raw)
This series makes implementing some of the bdrv_* callbacks easier for block
drivers by passing requests to bs->file if bs->drv doesn't implement it instead
of failing, and adding default bdrv_co_get_block_status() implementations.
This based against Kevin Wolf's block branch, commit
0dd2ec6bc46bd93ea0b9df602962883417f31400
Manos Pitsidianakis (2):
block: pass bdrv_* methods to bs->file by default
block: add default implementations for bdrv_co_get_block_status()
block.c | 45 ++++++++++++++++++++++++++++++++++-----------
block/blkdebug.c | 12 +-----------
block/commit.c | 12 +-----------
block/io.c | 28 ++++++++++++++++++++++++++++
block/mirror.c | 12 +-----------
include/block/block_int.h | 16 ++++++++++++++++
6 files changed, 81 insertions(+), 44 deletions(-)
--
2.11.0
next reply other threads:[~2017-06-27 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 22:46 Manos Pitsidianakis [this message]
2017-06-27 22:46 ` [Qemu-devel] [PATCH 1/2] block: pass bdrv_* methods to bs->file by default Manos Pitsidianakis
2017-06-29 14:00 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-06-29 14:05 ` Stefan Hajnoczi
2017-06-29 16:00 ` Eric Blake
2017-06-27 22:46 ` [Qemu-devel] [PATCH 2/2] block: add default implementations for bdrv_co_get_block_status() Manos Pitsidianakis
2017-06-29 14:04 ` [Qemu-devel] [Qemu-block] " 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=20170627224616.18538-1-el13635@mail.ntua.gr \
--to=el13635@mail.ntua.gr \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).