qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Emanuele Giuseppe Esposito <eesposit@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>,
	Kevin Wolf <kwolf@redhat.com>,
	qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
	Fam Zheng <fam@euphon.net>, Alberto Faria <afaria@redhat.com>,
	Hanna Reitz <hreitz@redhat.com>
Subject: Re: [PATCH] block: drop unused bdrv_co_drain() API
Date: Mon, 23 May 2022 10:02:54 +0200	[thread overview]
Message-ID: <d610a1f6-db5a-28c8-2cb7-5c383053b512@redhat.com> (raw)
In-Reply-To: <20220521122714.3837731-1-stefanha@redhat.com>



Am 21/05/2022 um 14:27 schrieb Stefan Hajnoczi:
> bdrv_co_drain() has not been used since commit 9a0cec664eef ("mirror:
> use bdrv_drained_begin/bdrv_drained_end") in 2016. Remove it so there
> are fewer drain scenarios to worry about.
> 
> Use bdrv_drained_begin()/bdrv_drained_end() instead. They are "mixed"
> functions that can be called from coroutine context. Unlike
> bdrv_co_drain(), these functions provide control of the length of the
> drained section, which is usually the right thing.
> 
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>

Reviewed-by: Emanuele Giuseppe Esposito <eesposit@redhat.com>

Thank you,
Emanuele

> ---
>  include/block/block-io.h |  1 -
>  block/io.c               | 15 ---------------
>  2 files changed, 16 deletions(-)
> 
> diff --git a/include/block/block-io.h b/include/block/block-io.h
> index 62c84f0519..053a27141a 100644
> --- a/include/block/block-io.h
> +++ b/include/block/block-io.h
> @@ -270,7 +270,6 @@ void bdrv_drained_end_no_poll(BlockDriverState *bs, int *drained_end_counter);
>                     cond); })
>  
>  void bdrv_drain(BlockDriverState *bs);
> -void coroutine_fn bdrv_co_drain(BlockDriverState *bs);
>  
>  int generated_co_wrapper
>  bdrv_truncate(BdrvChild *child, int64_t offset, bool exact,
> diff --git a/block/io.c b/block/io.c
> index 789e6373d5..1e9bf09a49 100644
> --- a/block/io.c
> +++ b/block/io.c
> @@ -588,21 +588,6 @@ void bdrv_unapply_subtree_drain(BdrvChild *child, BlockDriverState *old_parent)
>      BDRV_POLL_WHILE(child->bs, qatomic_read(&drained_end_counter) > 0);
>  }
>  
> -/*
> - * Wait for pending requests to complete on a single BlockDriverState subtree,
> - * and suspend block driver's internal I/O until next request arrives.
> - *
> - * Note that unlike bdrv_drain_all(), the caller must hold the BlockDriverState
> - * AioContext.
> - */
> -void coroutine_fn bdrv_co_drain(BlockDriverState *bs)
> -{
> -    IO_OR_GS_CODE();
> -    assert(qemu_in_coroutine());
> -    bdrv_drained_begin(bs);
> -    bdrv_drained_end(bs);
> -}
> -
>  void bdrv_drain(BlockDriverState *bs)
>  {
>      IO_OR_GS_CODE();
> 



  reply	other threads:[~2022-05-23  8:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-21 12:27 [PATCH] block: drop unused bdrv_co_drain() API Stefan Hajnoczi
2022-05-23  8:02 ` Emanuele Giuseppe Esposito [this message]
2022-05-23 19:39 ` Alberto Faria
2022-05-24 12:26 ` 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=d610a1f6-db5a-28c8-2cb7-5c383053b512@redhat.com \
    --to=eesposit@redhat.com \
    --cc=afaria@redhat.com \
    --cc=fam@euphon.net \
    --cc=hreitz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@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).