qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Max Reitz <mreitz@redhat.com>, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Peter Krempa <pkrempa@redhat.com>,
	Juan Quintela <quintela@redhat.com>, John Snow <jsnow@redhat.com>,
	qemu-devel@nongnu.org,
	"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH 0/4] migration: Add block-bitmap-mapping parameter
Date: Thu, 2 Jul 2020 14:24:23 +0300	[thread overview]
Message-ID: <b4ac8f7c-ebe9-6fa8-9b03-b12b457a3e5c@virtuozzo.com> (raw)
In-Reply-To: <20200630084552.46362-1-mreitz@redhat.com>

Hmm, seems, you didn't use scripts/get_maintainer.pl, as neither Eric nor John are in Cc. Add them.

30.06.2020 11:45, Max Reitz wrote:
> RFC v1: https://lists.nongnu.org/archive/html/qemu-block/2020-05/msg00912.html
> RFC v2: https://lists.nongnu.org/archive/html/qemu-block/2020-05/msg00915.html
> 
> Branch: https://github.com/XanClic/qemu.git migration-bitmap-mapping-v1
> Branch: https://git.xanclic.moe/XanClic/qemu.git migration-bitmap-mapping-v1
> 
> 
> Hi,
> 
> This new migration parameter allows mapping block node names and bitmap
> names to aliases for the purpose of block dirty bitmap migration.
> 
> This way, management tools can use different node names on the source
> and destination and pass the mapping of how bitmaps are to be
> transferred to qemu (on the source, the destination, or even both with
> arbitrary aliases in the migration stream).
> 
> v1 (as opposed to the RFC):
> - Added an iotest
> - Allow mapping of not only node names, but also of bitmap names to
>    aliases
> - Make this a migration parameter instead of adding a whole new QMP
>    command
> - Added patch 1 for good measure
> 
> 
> Max Reitz (4):
>    migration: Prevent memleak by ...params_test_apply
>    migration: Add block-bitmap-mapping parameter
>    iotests.py: Add wait_for_runstate()
>    iotests: Test node/bitmap aliases during migration
> 
>   qapi/migration.json            |  83 +++++-
>   migration/migration.h          |   3 +
>   migration/block-dirty-bitmap.c | 372 +++++++++++++++++++++----
>   migration/migration.c          |  33 ++-
>   tests/qemu-iotests/300         | 487 +++++++++++++++++++++++++++++++++
>   tests/qemu-iotests/300.out     |   5 +
>   tests/qemu-iotests/group       |   1 +
>   tests/qemu-iotests/iotests.py  |   4 +
>   8 files changed, 931 insertions(+), 57 deletions(-)
>   create mode 100755 tests/qemu-iotests/300
>   create mode 100644 tests/qemu-iotests/300.out
> 


-- 
Best regards,
Vladimir


      parent reply	other threads:[~2020-07-02 11:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30  8:45 [PATCH 0/4] migration: Add block-bitmap-mapping parameter Max Reitz
2020-06-30  8:45 ` [PATCH 1/4] migration: Prevent memleak by ...params_test_apply Max Reitz
2020-06-30 10:28   ` Dr. David Alan Gilbert
2020-07-01 11:10   ` Vladimir Sementsov-Ogievskiy
2020-07-01 14:38   ` Eric Blake
2020-07-02  8:14     ` Max Reitz
2020-06-30  8:45 ` [PATCH 2/4] migration: Add block-bitmap-mapping parameter Max Reitz
2020-06-30 10:51   ` Dr. David Alan Gilbert
2020-07-01 10:34     ` Max Reitz
2020-07-02 11:22       ` Dr. David Alan Gilbert
2020-07-01 14:34   ` Vladimir Sementsov-Ogievskiy
2020-07-02  8:09     ` Max Reitz
2020-07-02  9:19       ` Vladimir Sementsov-Ogievskiy
2020-07-02  9:41         ` Max Reitz
2020-07-02 10:40           ` Vladimir Sementsov-Ogievskiy
2020-07-02 10:49           ` Vladimir Sementsov-Ogievskiy
2020-07-02 13:04           ` Vladimir Sementsov-Ogievskiy
2020-06-30  8:45 ` [PATCH 3/4] iotests.py: Add wait_for_runstate() Max Reitz
2020-06-30  8:45 ` [PATCH 4/4] iotests: Test node/bitmap aliases during migration Max Reitz
2020-07-02 11:24 ` Vladimir Sementsov-Ogievskiy [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=b4ac8f7c-ebe9-6fa8-9b03-b12b457a3e5c@virtuozzo.com \
    --to=vsementsov@virtuozzo.com \
    --cc=dgilbert@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=pkrempa@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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).