From: John Snow <jsnow@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Fam Zheng <famz@redhat.com>,
Juan Quintela <quintela@redhat.com>,
qemu-stable@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH for-3.0 0/7] fix persistent bitmaps migration logic
Date: Mon, 30 Jul 2018 13:43:08 -0400 [thread overview]
Message-ID: <a55c92c1-d36f-8e56-5699-e5394399d2ae@redhat.com> (raw)
In-Reply-To: <153297036163.12997.1309407319525391577@sif>
On 07/30/2018 01:06 PM, Michael Roth wrote:
> Quoting John Snow (2018-07-23 17:22:03)
>> This is an updated version of Vladimir's proposal for fixing the
>> handling around migration and persistent dirty bitmaps.
>
> Are these still being considered for 3.0 rc3/rc4? 2.12.1 releases this week
> and I'm not sure how badly these are needed.
>
Good question. I'd still LIKE them in 3.0, but further fixes are
actually still needed, and I'm working on this right now.
I think you'll find that you might have trouble applying them to 2.12.1
without a fairly long trail of prerequisites, so it might not be easily
plausible.
>>
>> Patches 1, 4, 6, and 7 update the testing for this feature.
>> Patch 2 touches up an error message.
>> Patch 3 removes dead code.
>> Patch 5 contains the real fix.
>>
>> v2:
>> - Add a new patch 4 as a prerequisite for what's now patch 5
>> - Rework the fix to be (hopefully) cleaner, see patch 5 notes
>> - Adjust error message in patch 2 (Eric)
>> - Adjust test logic slightly (patches 6, 7) to deal with changes
>> in patch 5.
>>
>> John Snow (2):
>> iotests: 169: actually test block migration
>> dirty-bitmaps: clean-up bitmaps loading and migration logic
>>
>> Vladimir Sementsov-Ogievskiy (5):
>> iotests: 169: drop deprecated 'autoload' parameter
>> block/qcow2: improve error message in qcow2_inactivate
>> block/qcow2: drop dirty_bitmaps_loaded state variable
>> iotests: improve 169
>> iotests: 169: add cases for source vm resuming
>>
>> block.c | 4 ---
>> block/dirty-bitmap.c | 20 ------------
>> block/qcow2-bitmap.c | 16 +++++++++
>> block/qcow2.c | 26 ++++-----------
>> block/qcow2.h | 1 -
>> include/block/dirty-bitmap.h | 2 +-
>> migration/block-dirty-bitmap.c | 11 ++++---
>> tests/qemu-iotests/169 | 74 ++++++++++++++++++++++++++++++++++++++++--
>> tests/qemu-iotests/169.out | 4 +--
>> 9 files changed, 103 insertions(+), 55 deletions(-)
>>
>> --
>> 2.14.4
>>
>>
prev parent reply other threads:[~2018-07-30 17:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-23 22:22 [Qemu-devel] [PATCH for-3.0 0/7] fix persistent bitmaps migration logic John Snow
2018-07-23 22:22 ` [Qemu-devel] [PATCH for-3.0 1/7] iotests: 169: drop deprecated 'autoload' parameter John Snow
2018-07-23 22:22 ` [Qemu-devel] [PATCH for-3.0 2/7] block/qcow2: improve error message in qcow2_inactivate John Snow
2018-07-23 22:22 ` [Qemu-devel] [PATCH for-3.0 3/7] block/qcow2: drop dirty_bitmaps_loaded state variable John Snow
2018-07-23 22:22 ` [Qemu-devel] [PATCH for-3.0 4/7] iotests: 169: actually test block migration John Snow
2018-07-23 22:22 ` [Qemu-devel] [PATCH for-3.0 5/7] dirty-bitmaps: clean-up bitmaps loading and migration logic John Snow
2018-07-23 22:22 ` [Qemu-devel] [PATCH for-3.0 6/7] iotests: improve 169 John Snow
2018-07-23 22:22 ` [Qemu-devel] [PATCH for-3.0 7/7] iotests: 169: add cases for source vm resuming John Snow
2018-07-24 12:00 ` [Qemu-devel] [PATCH for-3.0 0/7] fix persistent bitmaps migration logic Stefan Hajnoczi
2018-07-30 17:06 ` Michael Roth
2018-07-30 17:43 ` John Snow [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=a55c92c1-d36f-8e56-5699-e5394399d2ae@redhat.com \
--to=jsnow@redhat.com \
--cc=dgilbert@redhat.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=quintela@redhat.com \
--cc=stefanha@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 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.