qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-block] [PATCH 1/2] iotests: Check dirty bitmap statistics in 124
Date: Mon, 24 Jul 2017 18:02:19 -0400	[thread overview]
Message-ID: <78846349-b145-a3a4-4e0f-8861b7423205@redhat.com> (raw)
In-Reply-To: <20170724153952.26510-2-eblake@redhat.com>



On 07/24/2017 11:39 AM, Eric Blake wrote:
> We had a bug for multiple releases where dirty-bitmap count was
> documented in bytes but reported in sectors; enhance the testsuite
> to add coverage of DirtyBitmapInfo to ensure we do not regress again.
> 
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
>   tests/qemu-iotests/124 | 7 ++++++-
>   1 file changed, 6 insertions(+), 1 deletion(-)
> 
> diff --git a/tests/qemu-iotests/124 b/tests/qemu-iotests/124
> index d0d2c2bfb0..8e76e62f93 100644
> --- a/tests/qemu-iotests/124
> +++ b/tests/qemu-iotests/124
> @@ -336,7 +336,12 @@ class TestIncrementalBackup(TestIncrementalBackupBase):
>                              (('0xab', 0, 512),
>                               ('0xfe', '16M', '256k'),
>                               ('0x64', '32736k', '64k')))
> -
> +        # Check the dirty bitmap stats
> +        result = self.vm.qmp('query-block')
> +        self.assert_qmp(result, 'return[0]/dirty-bitmaps[0]/name', 'bitmap0')
> +        self.assert_qmp(result, 'return[0]/dirty-bitmaps[0]/count', 458752)
> +        self.assert_qmp(result, 'return[0]/dirty-bitmaps[0]/granularity', 65536)
> +        self.assert_qmp(result, 'return[0]/dirty-bitmaps[0]/status', 'active')
> 
>           # Prepare a cluster_size=128k backup target without a backing file.
>           (target, _) = bitmap0.new_target()
> 

Good addition.

Reviewed-by: John Snow <jsnow@redhat.com>

  reply	other threads:[~2017-07-24 22:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-24 15:39 [Qemu-devel] [PATCH for-2.10 0/2] Test for bug fixes from byte-based block status Eric Blake
2017-07-24 15:39 ` [Qemu-devel] [PATCH 1/2] iotests: Check dirty bitmap statistics in 124 Eric Blake
2017-07-24 22:02   ` John Snow [this message]
2017-07-24 15:39 ` [Qemu-devel] [PATCH 2/2] iotests: Add test of recent fix to 'qemu-img measure' Eric Blake
2017-07-25 13:21 ` [Qemu-devel] [Qemu-block] [PATCH for-2.10 0/2] Test for bug fixes from byte-based block status Stefan Hajnoczi
2017-07-27 12:41 ` [Qemu-devel] " Kevin Wolf

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=78846349-b145-a3a4-4e0f-8861b7423205@redhat.com \
    --to=jsnow@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@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).