From: Juan Quintela <quintela@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] migration: remove subsections in fdc and rtl8139 and bump versions
Date: Wed, 03 Aug 2011 23:42:40 +0200 [thread overview]
Message-ID: <m3bow6cgtr.fsf@neno.neno> (raw)
In-Reply-To: <4E398A44.8060507@codemonkey.ws> (Anthony Liguori's message of "Wed, 03 Aug 2011 12:49:56 -0500")
Anthony Liguori <anthony@codemonkey.ws> wrote:
> On 08/03/2011 04:00 AM, Juan Quintela wrote:
> I don't have a problem with Paolo's new protocol. In fact, I'm strong
> in favor of applying it to master. But I don't like the idea of
> adding a new migration protocol with no testing in master before
> putting it in a release.
I have. If we are changing a protocol in an incompatible version, we
can remove a lot of warts that current descriptions have. Not that
Paolo protocol is bad, but if we are going to do some change, adding
things like size, removing previous warts, etc is the way to go.
>
>>>
>>> This series was just too late for 0.15. I can close to suggesting
>>> that we delay 0.15 in order to give this time to be tested thoroughly
>>> but I think my proposal is a reasonable compromise.
>>
>> I think it is anything except reasonable. From my point on view (and I
>> am biased), it is the equivalent of finding a corner case broken on
>> qcow2 and make all _OLD_ qcow2 images unreadable. It will work, but it
>> is anything except reasonable. As said, everything uses an fdc.
>> Furthermore, the _two_ things that you change don't matter in the big
>> scheme of things. The subsections that fail are the ones that can
>> appear in the middle of another section. The ones that appear at the
>> end of a real section work perfectly well with this protocol (a.k.a. the
>> ones that are broken are IDE), floppy and rtl8139 are ok with current
>> protocol.
>
> I can certainly limit the change to IDE if we think machine, floppy,
> and rtl8139 are safe.
Ok, only IDE is broken, something done if we are not reverting the others.
> My main concern is fixing the corruption during migration for the
> release. Once that is fixed, we can revisit compatibility for the
> stable branch (by introducing a compatibility path for the older
> version).
It is not possible to introduce that later. I very much prefer leave
things as they are, and add an stricter subsection test later.
Later, Juan.
next prev parent reply other threads:[~2011-08-03 21:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 23:08 [Qemu-devel] [PATCH] migration: remove subsections in fdc and rtl8139 and bump versions Anthony Liguori
2011-08-02 23:17 ` Anthony Liguori
2011-08-02 23:25 ` Juan Quintela
2011-08-03 0:12 ` Anthony Liguori
2011-08-03 6:44 ` Paolo Bonzini
2011-08-03 17:44 ` Anthony Liguori
2011-08-04 7:17 ` Paolo Bonzini
2011-08-03 9:00 ` Juan Quintela
2011-08-03 17:49 ` Anthony Liguori
2011-08-03 21:42 ` Juan Quintela [this message]
2011-08-04 7:22 ` Paolo Bonzini
2011-08-04 13:20 ` Anthony Liguori
2011-08-04 14:09 ` Kevin Wolf
2011-08-04 14:30 ` Anthony Liguori
2011-08-04 15:07 ` Paolo Bonzini
2011-08-04 20:31 ` Anthony Liguori
2011-08-04 12:59 ` Kevin Wolf
2011-08-04 13:12 ` Anthony Liguori
2011-08-04 14:36 ` Paolo Bonzini
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=m3bow6cgtr.fsf@neno.neno \
--to=quintela@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=pbonzini@redhat.com \
--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 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.