qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hanna Czenczek <hreitz@redhat.com>
To: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>, qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, kwolf@redhat.com, eblake@redhat.com,
	den@virtuozzo.com
Subject: Re: [PATCH v2 3/8] qemu-img: rebase: use backing files' BlockBackend for buffer alignment
Date: Tue, 19 Sep 2023 10:18:51 +0200	[thread overview]
Message-ID: <a4836464-22c3-2a49-0128-2dc4a98b5092@redhat.com> (raw)
In-Reply-To: <20230915162016.141771-4-andrey.drobyshev@virtuozzo.com>

On 15.09.23 18:20, Andrey Drobyshev wrote:
> Since commit bb1c05973cf ("qemu-img: Use qemu_blockalign"), buffers for
> the data read from the old and new backing files are aligned using
> BlockDriverState (or BlockBackend later on) referring to the target image.
> However, this isn't quite right, because buf_new is only being used for
> reading from the new backing, while buf_old is being used for both reading
> from the old backing and writing to the target.  Let's take that into account
> and use more appropriate values as alignments.
>
> Signed-off-by: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
> ---
>   qemu-img.c | 9 +++++++--
>   1 file changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/qemu-img.c b/qemu-img.c
> index 50660ba920..d12e4a4753 100644
> --- a/qemu-img.c
> +++ b/qemu-img.c
> @@ -3750,8 +3750,13 @@ static int img_rebase(int argc, char **argv)
>           int64_t n;
>           float local_progress = 0;
>   
> -        buf_old = blk_blockalign(blk, IO_BUF_SIZE);
> -        buf_new = blk_blockalign(blk, IO_BUF_SIZE);
> +        if (blk_old_backing && bdrv_opt_mem_align(blk_bs(blk)) >
> +            bdrv_opt_mem_align(blk_bs(blk_old_backing))) {
> +            buf_old = blk_blockalign(blk, IO_BUF_SIZE);
> +        } else {
> +            buf_old = blk_blockalign(blk_old_backing, IO_BUF_SIZE);
> +        }

As I read this, if blk_old_backing is NULL, we will go to the 
blk_blockalign(blk_old_backing, IO_BUF_SIZE) path.  I think if it is 
NULL, we should align on blk instead.

Hanna

> +        buf_new = blk_blockalign(blk_new_backing, IO_BUF_SIZE);
>   
>           size = blk_getlength(blk);
>           if (size < 0) {



  parent reply	other threads:[~2023-09-19  8:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-15 16:20 [PATCH v2 0/8] qemu-img: rebase: add compression support Andrey Drobyshev via
2023-09-15 16:20 ` [PATCH v2 1/8] qemu-img: rebase: stop when reaching EOF of old backing file Andrey Drobyshev via
2023-09-15 16:20 ` [PATCH v2 2/8] qemu-iotests: 024: add rebasing test case for overlay_size > backing_size Andrey Drobyshev via
2023-09-15 16:20 ` [PATCH v2 3/8] qemu-img: rebase: use backing files' BlockBackend for buffer alignment Andrey Drobyshev via
2023-09-15 18:39   ` Eric Blake
2023-09-15 19:27     ` Andrey Drobyshev
2023-09-19  8:18   ` Hanna Czenczek [this message]
2023-09-19  9:26     ` Andrey Drobyshev
2023-09-15 16:20 ` [PATCH v2 4/8] qemu-img: add chunk size parameter to compare_buffers() Andrey Drobyshev via
2023-09-15 19:28   ` Eric Blake
2023-09-19  8:32   ` Hanna Czenczek
2023-09-15 16:20 ` [PATCH v2 5/8] qemu-img: rebase: avoid unnecessary COW operations Andrey Drobyshev via
2023-09-15 21:52   ` Eric Blake
2023-09-16 17:45     ` Andrey Drobyshev
2023-09-19 10:46   ` Hanna Czenczek
2023-09-19 16:21     ` Andrey Drobyshev
2023-09-15 16:20 ` [PATCH v2 6/8] iotests/{024, 271}: add testcases for qemu-img rebase Andrey Drobyshev via
2023-09-19 11:08   ` Hanna Czenczek
2023-09-15 16:20 ` [PATCH v2 7/8] qemu-img: add compression option to rebase subcommand Andrey Drobyshev via
2023-09-15 16:20 ` [PATCH v2 8/8] iotests: add tests for "qemu-img rebase" with compression Andrey Drobyshev via
2023-09-19 11:14   ` Hanna Czenczek

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=a4836464-22c3-2a49-0128-2dc4a98b5092@redhat.com \
    --to=hreitz@redhat.com \
    --cc=andrey.drobyshev@virtuozzo.com \
    --cc=den@virtuozzo.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /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).