qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Fam Zheng <famz@redhat.com>, qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
	qemu-stable@nongnu.org, qemu-block@nongnu.org,
	wangxiaolong@ucloud.cn
Subject: Re: [Qemu-devel] [PATCH v4 3/8] mirror: Do zero write on target if sectors not allocated
Date: Mon, 25 May 2015 16:41:00 +0200	[thread overview]
Message-ID: <5563347C.10900@redhat.com> (raw)
In-Reply-To: <5563337C.6010009@redhat.com>



On 25/05/2015 16:36, Paolo Bonzini wrote:
> 
> 
> On 22/05/2015 05:40, Fam Zheng wrote:
>> +    ret = bdrv_get_block_status(source, NULL, sector_num, nb_sectors, &pnum);
>> +    if (ret < 0 || pnum < nb_sectors ||
>> +            (ret & BDRV_BLOCK_ALLOCATED && !(ret & BDRV_BLOCK_ZERO))) {
>> +        bdrv_aio_readv(source, sector_num, &op->qiov, nb_sectors,
>> +                       mirror_read_complete, op);
>> +    } else if (ret & BDRV_BLOCK_ZERO) {
>> +        bdrv_aio_write_zeroes(s->target, sector_num, op->nb_sectors,
>> +                              s->unmap ? BDRV_REQ_MAY_UNMAP : 0,
>> +                              mirror_write_complete, op);
>> +    } else {
>> +        assert(!(ret & BDRV_BLOCK_ALLOCATED));
>> +        bdrv_aio_discard(s->target, sector_num, op->nb_sectors,
>> +                         mirror_write_complete, op);
>> +    }
> 
> This doesn't work if you have a backing file.  You want to test
> BDRV_BLOCK_DATA, not BDRV_BLOCK_ALLOCATED.
> 
> On the other hand, if BDRV_BLOCK_ALLOCATED is nonzero, you need to
> recurse on bs->backing_hd.  The logic is very similar to
> bdrv_is_allocated_above, but you need to write bdrv_get_block_status_above.

Oops, I totally missed the "NULL" in the first line.  Still, I think
BDRV_BLOCK_DATA is a better check than BDRV_BLOCK_ALLOCATED.

Paolo

  reply	other threads:[~2015-05-25 14:41 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
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 [this message]
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=5563347C.10900@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=famz@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).