From: John Snow <jsnow@redhat.com>
To: Max Reitz <mreitz@redhat.com>, qemu-block@nongnu.org
Cc: vsementsov@virtuozzo.com, famz@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v6 09/10] tests: Add test code for hbitmap serialization
Date: Mon, 18 Jul 2016 15:45:31 -0400 [thread overview]
Message-ID: <dfe47a0e-fbc3-af2e-c1d7-fd460b8f1d50@redhat.com> (raw)
In-Reply-To: <056434cd-8a6e-7ae7-9ea9-9ab922091c7c@redhat.com>
On 07/18/2016 11:24 AM, Max Reitz wrote:
> On 15.07.2016 22:27, John Snow wrote:
>> From: Fam Zheng <famz@redhat.com>
>>
>> Acked-by: John Snow <jsnow@redhat.com>
>> Signed-off-by: Fam Zheng <famz@redhat.com>
>> Signed-off-by: John Snow <jsnow@redhat.com>
>> ---
>> tests/test-hbitmap.c | 139 +++++++++++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 139 insertions(+)
>>
>> diff --git a/tests/test-hbitmap.c b/tests/test-hbitmap.c
>> index e3abde1..18e8114 100644
>> --- a/tests/test-hbitmap.c
>> +++ b/tests/test-hbitmap.c
>
> [...]
>
>> @@ -737,6 +738,16 @@ static void test_hbitmap_meta_one(TestHBitmapData *data, const void *unused)
>> }
>> }
>>
>> +static void test_hbitmap_serialize_granularity(TestHBitmapData *data,
>> + const void *unused)
>> +{
>> + int r;
>> +
>> + hbitmap_test_init(data, L3 * 2, 3);
>> + r = hbitmap_serialization_granularity(data->hb);
>> + g_assert_cmpint(r, ==, BITS_PER_LONG << 3);
>
> Won't this only work on systems where BITS_PER_LONG == 64?
> (Because hbitmap_serialization_granularity() uses a hard-coded 64.)
>
> Rest looks good.
>
> Max
>
Yes, good catch.
>> +}
>> +
>> static void test_hbitmap_meta_zero(TestHBitmapData *data, const void *unused)
>> {
>> hbitmap_test_init_meta(data, 0, 0, 1);
>
next prev parent reply other threads:[~2016-07-18 19:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 20:27 [Qemu-devel] [PATCH v6 00/10] Dirty bitmap changes for migration/persistence work John Snow
2016-07-15 20:27 ` [Qemu-devel] [PATCH v6 01/10] block: Hide HBitmap in block dirty bitmap interface John Snow
2016-07-15 20:27 ` [Qemu-devel] [PATCH v6 02/10] HBitmap: Introduce "meta" bitmap to track bit changes John Snow
2016-07-18 14:54 ` Max Reitz
2016-07-15 20:27 ` [Qemu-devel] [PATCH v6 03/10] tests: Add test code for meta bitmap John Snow
2016-07-15 20:27 ` [Qemu-devel] [PATCH v6 04/10] block: Support meta dirty bitmap John Snow
2016-07-18 14:57 ` Max Reitz
2016-07-18 16:24 ` John Snow
2016-07-15 20:27 ` [Qemu-devel] [PATCH v6 05/10] block: Add two dirty bitmap getters John Snow
2016-07-15 20:27 ` [Qemu-devel] [PATCH v6 06/10] block: Assert that bdrv_release_dirty_bitmap succeeded John Snow
2016-07-15 20:27 ` [Qemu-devel] [PATCH v6 07/10] hbitmap: serialization John Snow
2016-07-15 20:27 ` [Qemu-devel] [PATCH v6 08/10] block: BdrvDirtyBitmap serialization interface John Snow
2016-07-18 15:11 ` Max Reitz
2016-07-15 20:27 ` [Qemu-devel] [PATCH v6 09/10] tests: Add test code for hbitmap serialization John Snow
2016-07-18 15:24 ` Max Reitz
2016-07-18 19:45 ` John Snow [this message]
2016-07-15 20:27 ` [Qemu-devel] [PATCH v6 10/10] block: More operations for meta dirty bitmap John Snow
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=dfe47a0e-fbc3-af2e-c1d7-fd460b8f1d50@redhat.com \
--to=jsnow@redhat.com \
--cc=famz@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.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).