From: Anthony Liguori <anthony@codemonkey.ws>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] migration: remove subsections in fdc and rtl8139 and bump versions (v2)
Date: Wed, 03 Aug 2011 12:45:46 -0500 [thread overview]
Message-ID: <4E39894A.3060000@codemonkey.ws> (raw)
In-Reply-To: <4E390810.2040809@redhat.com>
On 08/03/2011 03:34 AM, Kevin Wolf wrote:
> Am 03.08.2011 02:18, schrieb Anthony Liguori:
>> As Paolo points out, the migration protocol is ambiguous when using subsections
>> today. That means that even if we preserve subsections and change the protocol
>> accordingly, the old protocol w/subsections is still ambiguous.
>>
>> Remove subsection usage and bump any device using subsections. This effectively
>> eliminates the amiguouity and allows for a clean transition to a new protocol
>> with unambiguous subsections.
>>
>> Signed-off-by: Anthony Liguori<aliguori@us.ibm.com>
>> --
>> v1 -> v2
>> - Also remove IDE subsections (spotted by Juan Quintela)
>
> Please remove migration_compat_status from BMDMAState and the respective
> VMState, there's no reason for it any more when you increase the version
> number.
Thanks for the confirmation. I suspected that but I figured that a more
conservative approach was safer.
Regards,
Anthony Liguori
>
> Kevin
>
prev parent reply other threads:[~2011-08-03 17:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-03 0:18 [Qemu-devel] [PATCH] migration: remove subsections in fdc and rtl8139 and bump versions (v2) Anthony Liguori
2011-08-03 5:53 ` Jan Kiszka
2011-08-03 8:34 ` Kevin Wolf
2011-08-03 17:45 ` Anthony Liguori [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=4E39894A.3060000@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aliguori@us.ibm.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--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).