From: "Denis V. Lunev" <den-lists@virtuozzo.com>
To: Ren Kimura <rkx1209dev@gmail.com>, mreitz@redhat.com
Cc: kwolf@redhat.com, qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] qemu-img: check block status of backing file when converting.
Date: Thu, 21 Apr 2016 09:53:18 +0300 [thread overview]
Message-ID: <571878DE.80405@virtuozzo.com> (raw)
In-Reply-To: <1460867433-13251-1-git-send-email-rkx1209dev@gmail.com>
On 04/17/2016 07:30 AM, Ren Kimura wrote:
> When converting images, check the block status of its backing file chain
> to avoid needlessly reading zeros.
>
> Signed-off-by: Ren Kimura <rkx1209dev@gmail.com>
IMHO bdrv_get_block_status_above(bs, NULL, ...) should do the job
without recursion.
prev parent reply other threads:[~2016-04-21 7:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-17 4:30 [Qemu-devel] [PATCH v3] qemu-img: check block status of backing file when converting Ren Kimura
2016-04-21 5:28 ` Ren Kimura
2016-04-21 6:53 ` Denis V. Lunev [this message]
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=571878DE.80405@virtuozzo.com \
--to=den-lists@virtuozzo.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rkx1209dev@gmail.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).