qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fam Zheng <famz@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
	qemu-block@nongnu.org, Jeff Cody <jcody@redhat.com>,
	qemu-devel@nongnu.org, qemu-stable@nongnu.org,
	Stefan Hajnoczi <stefanha@redhat.com>,
	jsnow@redhat.com, wangxiaolong@ucloud.cn
Subject: Re: [Qemu-devel] [PATCH v4 1/8] block: Add "base" option to bdrv_get_block_status
Date: Tue, 26 May 2015 11:30:14 +0800	[thread overview]
Message-ID: <20150526033014.GA5044@ad.nay.redhat.com> (raw)
In-Reply-To: <55633519.9030407@redhat.com>

On Mon, 05/25 16:43, Paolo Bonzini wrote:
> 
> 
> On 22/05/2015 05:40, Fam Zheng wrote:
> > +{
> > +    BlockDriverState *p;
> > +    int64_t ret;
> > +
> > +    assert(bs != base);
> > +    for (p = bs; p != base; p = p->backing_hd) {
> > +        ret = bdrv_co_get_block_status(p, sector_num, nb_sectors, pnum);
> 
> It's a bit ugly to have different parameters for bdrv_get_block_status
> and bdrv_co_get_block_status.

I'll add bdrv_get_block_status_above and rewrite bdrv_get_block_status body on
top.

> 
> > +        if (ret < 0 || ret & BDRV_BLOCK_ALLOCATED) {
> > +            break;
> > +        }
> > +    }
> > +    return ret;
> > +}
> > +
> 
> I think BDRV_BLOCK_ALLOCATED will always be true if passing NULL as the
> base, so patch 3 still needs a tweak.

OK, will use BDRV_BLOCK_DATA there.

> 
> But, more important, you need extra logic to correct the output value of
> pnum, as in bdrv_is_allocated_above.

bdrv_co_get_block_status should fix pnum.

Fam

  reply	other threads:[~2015-05-26  3:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-22  3:40 [Qemu-devel] [PATCH v4 0/8] block: Mirror discarded sectors Fam Zheng
2015-05-22  3:40 ` [Qemu-devel] [PATCH v4 1/8] block: Add "base" option to bdrv_get_block_status Fam Zheng
2015-05-22 19:32   ` Eric Blake
2015-05-25 14:43   ` Paolo Bonzini
2015-05-26  3:30     ` Fam Zheng [this message]
2015-05-22  3:40 ` [Qemu-devel] [PATCH v4 2/8] qmp: Add optional bool "unmap" to drive-mirror Fam Zheng
2015-05-22 19:57   ` Eric Blake
2015-05-22  3:40 ` [Qemu-devel] [PATCH v4 3/8] mirror: Do zero write on target if sectors not allocated Fam Zheng
2015-05-22 20:20   ` Eric Blake
2015-05-25 14:38     ` Paolo Bonzini
2015-05-25 14:36   ` Paolo Bonzini
2015-05-25 14:41     ` Paolo Bonzini
2015-05-22  3:40 ` [Qemu-devel] [PATCH v4 4/8] block: Fix dirty bitmap in bdrv_co_discard Fam Zheng
2015-05-22 20:22   ` Eric Blake
2015-05-22  3:40 ` [Qemu-devel] [PATCH v4 5/8] block: Remove bdrv_reset_dirty Fam Zheng
2015-05-22  3:40 ` [Qemu-devel] [PATCH v4 6/8] qemu-iotests: Make block job methods common Fam Zheng
2015-05-22  3:40 ` [Qemu-devel] [PATCH v4 7/8] qemu-iotests: Add test case for mirror with unmap Fam Zheng
2015-05-22  3:41 ` [Qemu-devel] [PATCH v4 8/8] iotests: Use event_wait in wait_ready 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=20150526033014.GA5044@ad.nay.redhat.com \
    --to=famz@redhat.com \
    --cc=jcody@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=wangxiaolong@ucloud.cn \
    /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).