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 v8 00/10] Dirty bitmap changes for migration/persistence work
Date: Wed, 3 Aug 2016 13:00:16 -0400 [thread overview]
Message-ID: <43d6bc91-71c9-2584-abec-c091e4ba38d7@redhat.com> (raw)
In-Reply-To: <81a551fd-7a28-9b85-4ae3-2fd0e2a66f3a@redhat.com>
On 08/03/2016 12:44 PM, Max Reitz wrote:
> On 02.08.2016 02:12, John Snow wrote:
>> Key:
>> [----] : patches are identical
>> [####] : number of functional differences between upstream/downstream patch
>> [down] : patch is downstream-only
>> The flags [FC] indicate (F)unctional and (C)ontextual differences, respectively
>>
>> 001/10:[----] [-C] 'block: Hide HBitmap in block dirty bitmap interface'
>> 002/10:[----] [--] 'HBitmap: Introduce "meta" bitmap to track bit changes'
>> 003/10:[----] [--] 'tests: Add test code for meta bitmap'
>> 004/10:[0004] [FC] 'block: Support meta dirty bitmap'
>> 005/10:[----] [--] 'block: Add two dirty bitmap getters'
>> 006/10:[----] [--] 'block: Assert that bdrv_release_dirty_bitmap succeeded'
>> 007/10:[----] [--] 'hbitmap: serialization'
>> 008/10:[----] [-C] 'block: BdrvDirtyBitmap serialization interface'
>> 009/10:[----] [--] 'tests: Add test code for hbitmap serialization'
>> 010/10:[----] [--] 'block: More operations for meta dirty bitmap'
>>
>> ===
>> v8: Hello, is it v8 you're looking for?
>> ===
>
> Thanks, queued for 2.8:
>
> https://github.com/XanClic/qemu/commits/block-next
>
> (Any volunteers for a MAINTAINERS entry regarding the bitmap code? :-))
>
> Max
>
Fam and I as co-maintainers, perhaps?
--js
next prev parent reply other threads:[~2016-08-03 17:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-02 0:12 [Qemu-devel] [PATCH v8 00/10] Dirty bitmap changes for migration/persistence work John Snow
2016-08-02 0:12 ` [Qemu-devel] [PATCH v8 01/10] block: Hide HBitmap in block dirty bitmap interface John Snow
2016-08-02 0:12 ` [Qemu-devel] [PATCH v8 02/10] HBitmap: Introduce "meta" bitmap to track bit changes John Snow
2016-08-02 0:12 ` [Qemu-devel] [PATCH v8 03/10] tests: Add test code for meta bitmap John Snow
2016-08-02 0:12 ` [Qemu-devel] [PATCH v8 04/10] block: Support meta dirty bitmap John Snow
2016-08-03 16:23 ` Max Reitz
2016-08-02 0:12 ` [Qemu-devel] [PATCH v8 05/10] block: Add two dirty bitmap getters John Snow
2016-08-02 0:12 ` [Qemu-devel] [PATCH v8 06/10] block: Assert that bdrv_release_dirty_bitmap succeeded John Snow
2016-08-02 0:12 ` [Qemu-devel] [PATCH v8 07/10] hbitmap: serialization John Snow
2016-09-17 21:31 ` Max Reitz
2016-08-02 0:12 ` [Qemu-devel] [PATCH v8 08/10] block: BdrvDirtyBitmap serialization interface John Snow
2016-08-02 0:12 ` [Qemu-devel] [PATCH v8 09/10] tests: Add test code for hbitmap serialization John Snow
2016-08-02 0:12 ` [Qemu-devel] [PATCH v8 10/10] block: More operations for meta dirty bitmap John Snow
2016-08-03 16:44 ` [Qemu-devel] [PATCH v8 00/10] Dirty bitmap changes for migration/persistence work Max Reitz
2016-08-03 17:00 ` John Snow [this message]
2016-08-04 1:26 ` 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=43d6bc91-71c9-2584-abec-c091e4ba38d7@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.