qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
	qemu-block@nongnu.org
Cc: fam@euphon.net, kwolf@redhat.com,
	Alberto Garcia <berto@igalia.com>,
	qemu-devel@nongnu.org, mreitz@redhat.com, stefanha@redhat.com,
	den@openvz.org
Subject: Re: [PATCH v7 2/5] block/io: bdrv_common_block_status_above: support include_base
Date: Thu, 24 Sep 2020 15:07:14 -0500	[thread overview]
Message-ID: <f18a7304-e373-2126-d06f-5ef20323180b@redhat.com> (raw)
In-Reply-To: <20200924194003.22080-3-vsementsov@virtuozzo.com>

On 9/24/20 2:40 PM, Vladimir Sementsov-Ogievskiy wrote:
> In order to reuse bdrv_common_block_status_above in
> bdrv_is_allocated_above, let's support include_base parameter.
> 
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> Reviewed-by: Alberto Garcia <berto@igalia.com>
> ---
>   block/coroutines.h |  2 ++
>   block/io.c         | 21 ++++++++++++++-------
>   2 files changed, 16 insertions(+), 7 deletions(-)
> 

> +++ b/block/io.c
> @@ -2343,6 +2343,7 @@ early_out:
>   int coroutine_fn
>   bdrv_co_common_block_status_above(BlockDriverState *bs,
>                                     BlockDriverState *base,
> +                                  bool include_base,
>                                     bool want_zero,
>                                     int64_t offset,
>                                     int64_t bytes,
> @@ -2354,10 +2355,11 @@ bdrv_co_common_block_status_above(BlockDriverState *bs,
>       BlockDriverState *p;
>       int64_t eof = 0;
>   
> -    assert(bs != base);
> +    assert(include_base || bs != base);
> +    assert(!include_base || base); /* Can't include NULL base */

I wonder if this would be easier to read as:

if (include_base) {
     assert(bs != base);
} else {
     assert(base); /* Can't include NULL base */
}

but I won't insist.

Reviewed-by: Eric Blake <eblake@redhat.com>

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org



  reply	other threads:[~2020-09-24 20:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-24 19:39 [PATCH v7 0/5] fix & merge block_status_above and is_allocated_above Vladimir Sementsov-Ogievskiy
2020-09-24 19:39 ` [PATCH v7 1/5] block/io: fix bdrv_co_block_status_above Vladimir Sementsov-Ogievskiy
2020-09-24 20:01   ` Eric Blake
2020-09-24 19:40 ` [PATCH v7 2/5] block/io: bdrv_common_block_status_above: support include_base Vladimir Sementsov-Ogievskiy
2020-09-24 20:07   ` Eric Blake [this message]
2020-09-24 19:40 ` [PATCH v7 3/5] block/io: bdrv_common_block_status_above: support bs == base Vladimir Sementsov-Ogievskiy
2020-09-24 19:40 ` [PATCH v7 4/5] block/io: fix bdrv_is_allocated_above Vladimir Sementsov-Ogievskiy
2020-09-24 20:11   ` Eric Blake
2020-09-24 19:40 ` [PATCH v7 5/5] iotests: add commit top->base cases to 274 Vladimir Sementsov-Ogievskiy
2020-09-24 21:45 ` [PATCH v7 0/5] fix & merge block_status_above and is_allocated_above no-reply
2020-09-25  8:38   ` Vladimir Sementsov-Ogievskiy
2020-10-09 10:15 ` 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=f18a7304-e373-2126-d06f-5ef20323180b@redhat.com \
    --to=eblake@redhat.com \
    --cc=berto@igalia.com \
    --cc=den@openvz.org \
    --cc=fam@euphon.net \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vsementsov@virtuozzo.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).