From: Kevin Wolf <kwolf@redhat.com>
To: qemu-block@nongnu.org
Cc: kwolf@redhat.com, eblake@redhat.com, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v2 0/4] Block migration (migrate -b) fixes
Date: Tue, 30 May 2017 17:22:49 +0200 [thread overview]
Message-ID: <1496157773-10779-1-git-send-email-kwolf@redhat.com> (raw)
v2:
- Detect when migrate -b is compiled out [Eric]
- Switched the whole test to QMP for this, HMP is a bit hard to
deal with
Kevin Wolf (4):
block: Fix anonymous BBs in blk_root_inactivate()
migration: Inactivate images after .save_live_complete_precopy()
migration/block: Clean up BBs in block_save_complete()
qemu-iotests: Block migration test
block/block-backend.c | 2 +-
migration/block.c | 22 +++++--
migration/migration.c | 12 ++--
tests/qemu-iotests/183 | 143 +++++++++++++++++++++++++++++++++++++++++++++
tests/qemu-iotests/183.out | 46 +++++++++++++++
tests/qemu-iotests/group | 1 +
6 files changed, 215 insertions(+), 11 deletions(-)
create mode 100755 tests/qemu-iotests/183
create mode 100644 tests/qemu-iotests/183.out
--
1.8.3.1
next reply other threads:[~2017-05-30 15:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 15:22 Kevin Wolf [this message]
2017-05-30 15:22 ` [Qemu-devel] [PATCH v2 1/4] block: Fix anonymous BBs in blk_root_inactivate() Kevin Wolf
2017-05-30 15:28 ` [Qemu-devel] [Qemu-block] " Jeff Cody
2017-05-30 15:22 ` [Qemu-devel] [PATCH v2 2/4] migration: Inactivate images after .save_live_complete_precopy() Kevin Wolf
2017-05-30 15:29 ` [Qemu-devel] [Qemu-block] " Jeff Cody
2017-05-30 15:22 ` [Qemu-devel] [PATCH v2 3/4] migration/block: Clean up BBs in block_save_complete() Kevin Wolf
2017-05-30 15:32 ` [Qemu-devel] [Qemu-block] " Jeff Cody
2017-05-30 15:22 ` [Qemu-devel] [PATCH v2 4/4] qemu-iotests: Block migration test Kevin Wolf
2017-05-30 15:52 ` [Qemu-devel] [Qemu-block] " Jeff Cody
2017-05-30 16:57 ` Kevin Wolf
2017-05-30 18:48 ` Jeff Cody
2017-05-31 9:00 ` Kevin Wolf
2017-05-30 16:03 ` [Qemu-devel] " Eric Blake
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=1496157773-10779-1-git-send-email-kwolf@redhat.com \
--to=kwolf@redhat.com \
--cc=eblake@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).