qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH 7/8] block: change flush to co_flush
Date: Thu, 20 Oct 2011 12:04:08 +0200	[thread overview]
Message-ID: <4E9FF218.7010208@redhat.com> (raw)
In-Reply-To: <1319036398-14320-8-git-send-email-pbonzini@redhat.com>

Am 19.10.2011 16:59, schrieb Paolo Bonzini:
> Since coroutine operation is now mandatory, convert all bdrv_flush
> implementations to coroutines.  For qcow2, this means taking the lock.
> Other implementations are simpler and just forward bdrv_flush to the
> underlying protocol, so they can avoid the lock.
> 
> The bdrv_flush callback is then unused and can be eliminated.
> 
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>

> diff --git a/block/qcow.c b/block/qcow.c
> index f93e3eb..61f73d6 100644
> --- a/block/qcow.c
> +++ b/block/qcow.c
> @@ -781,10 +781,9 @@ static int qcow_write_compressed(BlockDriverState *bs, int64_t sector_num,
>      return 0;
>  }
>  
> -static BlockDriverAIOCB *qcow_aio_flush(BlockDriverState *bs,
> -        BlockDriverCompletionFunc *cb, void *opaque)
> +static coroutine_fn int qcow_co_flush(BlockDriverState *bs)
>  {
> -    return bdrv_aio_flush(bs->file, cb, opaque);
> +    return bdrv_co_flush(bs->file);
>  }
>  
>  static int qcow_get_info(BlockDriverState *bs, BlockDriverInfo *bdi)
> @@ -824,9 +823,9 @@ static BlockDriver bdrv_qcow = {
>      .bdrv_is_allocated	= qcow_is_allocated,
>      .bdrv_set_key	= qcow_set_key,
>      .bdrv_make_empty	= qcow_make_empty,
> -    .bdrv_co_readv  = qcow_co_readv,
> -    .bdrv_co_writev = qcow_co_writev,
> -    .bdrv_aio_flush	= qcow_aio_flush,
> +    .bdrv_co_readv      = qcow_co_readv,
> +    .bdrv_co_writev     = qcow_co_writev,
> +    .bdrv_co_flush	= qcow_co_flush,
>      .bdrv_write_compressed = qcow_write_compressed,
>      .bdrv_get_info	= qcow_get_info,

Please don't add new tabs, use spaces instead. (Same thing in other drivers)

The logic looks good to me.

Kevin

  reply	other threads:[~2011-10-20 10:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19 14:59 [Qemu-devel] [PATCH 0/8] finish coroutinization of drivers Paolo Bonzini
2011-10-19 14:59 ` [Qemu-devel] [PATCH 1/8] vpc: detect floppy disk geometries Paolo Bonzini
2011-10-20  9:14   ` Kevin Wolf
2011-10-20 10:13     ` Paolo Bonzini
2011-10-19 14:59 ` [Qemu-devel] [PATCH 2/8] vmdk: fix return values of vmdk_parent_open Paolo Bonzini
2011-10-20  9:16   ` Kevin Wolf
2011-10-19 14:59 ` [Qemu-devel] [PATCH 3/8] vmdk: clean up open Paolo Bonzini
2011-10-20  9:28   ` Kevin Wolf
2011-10-20 10:12     ` Paolo Bonzini
2011-10-20 10:25       ` Kevin Wolf
2011-10-19 14:59 ` [Qemu-devel] [PATCH 4/8] block: add a Rwlock to synchronous read/write drivers Paolo Bonzini
2011-10-20  9:47   ` Kevin Wolf
2011-10-19 14:59 ` [Qemu-devel] [PATCH 5/8] block: take lock around bdrv_read implementations Paolo Bonzini
2011-10-19 14:59 ` [Qemu-devel] [PATCH 6/8] block: take lock around bdrv_write implementations Paolo Bonzini
2011-10-19 14:59 ` [Qemu-devel] [PATCH 7/8] block: change flush to co_flush Paolo Bonzini
2011-10-20 10:04   ` Kevin Wolf [this message]
2011-10-19 14:59 ` [Qemu-devel] [PATCH 8/8] block: change discard to co_discard Paolo Bonzini
2011-10-20 10:08   ` Kevin Wolf

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=4E9FF218.7010208@redhat.com \
    --to=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@linux.vnet.ibm.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).