qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	qemu-block@nongnu.org, qemu-devel@nongnu.org,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 11/12] qed: Implement .bdrv_drain
Date: Mon, 12 Oct 2015 16:23:09 +0200	[thread overview]
Message-ID: <20151012142309.GH4153@noname.str.redhat.com> (raw)
In-Reply-To: <1444650651-26227-12-git-send-email-famz@redhat.com>

Am 12.10.2015 um 13:50 hat Fam Zheng geschrieben:
> The "need_check_timer" is used to clear the "NEED_CHECK" flag in the
> image header after a grace period once metadata update has finished. In
> compliance to the bdrv_drain semantics we should make sure it remains
> deleted once .bdrv_drain is called.
> 
> Call the qed_need_check_timer_cb manually to update the header
> immediately.
> 
> Signed-off-by: Fam Zheng <famz@redhat.com>

What happens if a new allocating write request is issued during the
drained section and the timer gets reenabled?

Kevin

>  block/qed.c | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/block/qed.c b/block/qed.c
> index a7ff1d9..23bd273 100644
> --- a/block/qed.c
> +++ b/block/qed.c
> @@ -381,6 +381,12 @@ static void bdrv_qed_attach_aio_context(BlockDriverState *bs,
>      }
>  }
>  
> +static void bdrv_qed_drain(BlockDriverState *bs)
> +{
> +    qed_cancel_need_check_timer(bs->opaque);
> +    qed_need_check_timer_cb(bs->opaque);
> +}
> +
>  static int bdrv_qed_open(BlockDriverState *bs, QDict *options, int flags,
>                           Error **errp)
>  {
> @@ -1683,6 +1689,7 @@ static BlockDriver bdrv_qed = {
>      .bdrv_check               = bdrv_qed_check,
>      .bdrv_detach_aio_context  = bdrv_qed_detach_aio_context,
>      .bdrv_attach_aio_context  = bdrv_qed_attach_aio_context,
> +    .bdrv_drain               = bdrv_qed_drain,
>  };
>  
>  static void bdrv_qed_init(void)
> -- 
> 2.6.1
> 

  reply	other threads:[~2015-10-12 14:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-12 11:50 [Qemu-devel] [PATCH v2 00/12] block: bdrv_drained_begin/end for transactions on dataplane devices Fam Zheng
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 01/12] aio: Add "is_external" flag for event handlers Fam Zheng
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 02/12] nbd: Mark fd handlers client type as "external" Fam Zheng
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 03/12] dataplane: Mark host notifiers' " Fam Zheng
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 04/12] aio: introduce aio_{disable, enable}_external Fam Zheng
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 05/12] block: Introduce "drained begin/end" API Fam Zheng
2015-10-12 13:59   ` Kevin Wolf
2015-10-12 14:27   ` Paolo Bonzini
2015-10-13  9:31     ` Kevin Wolf
2015-10-13 10:39       ` Paolo Bonzini
2015-10-13 11:12         ` Kevin Wolf
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 06/12] block: Add "drained begin/end" for transactional external snapshot Fam Zheng
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 07/12] block: Add "drained begin/end" for transactional backup Fam Zheng
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 08/12] block: Add "drained begin/end" for transactional blockdev-backup Fam Zheng
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 09/12] block: Add "drained begin/end" for internal snapshot Fam Zheng
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 10/12] block: Introduce BlockDriver.bdrv_drain callback Fam Zheng
2015-10-12 14:17   ` Kevin Wolf
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 11/12] qed: Implement .bdrv_drain Fam Zheng
2015-10-12 14:23   ` Kevin Wolf [this message]
2015-10-12 11:50 ` [Qemu-devel] [PATCH v2 12/12] tests: Add test case for aio_disable_external Fam Zheng

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=20151012142309.GH4153@noname.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=famz@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).