From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: amit.shah@redhat.com, qemu-devel@nongnu.org,
"Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>,
quintela@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Migration compatibility for serial
Date: Wed, 17 Jun 2015 13:33:26 +0200 [thread overview]
Message-ID: <55815B06.5030508@redhat.com> (raw)
In-Reply-To: <20150617121148-mutt-send-email-mst@redhat.com>
On 17/06/2015 12:13, Michael S. Tsirkin wrote:
> On Wed, Jun 17, 2015 at 10:11:48AM +0200, Paolo Bonzini wrote:
>>
>>
>> On 17/06/2015 09:52, Michael S. Tsirkin wrote:
>>>> No, please. Upstream QEMU doesn't want to get into judgement about when
>>>> migration quality might be "good enough" that you can drop subsections.
>>>> It's one thing to perfect the .needed functions to make the appearance
>>>> of subsections as unlikely as possible, but adding flags is not
>>>> something we've done so far---and not something at least *I* want to do.
>>>
>>> Not like this, sure. But e.g. patches that force specific fields to
>>> behave in a way consistent with QEMU 2.2, with appropriate
>>> doducmentation would be ok I think.
>>
>> That's not what 2.2 means in "pc-i440fx-2.2". It means "same hardware
>> as 2.2", not "bug-compatible with 2.2".
>>
>> Refining the .needed functions (e.g. see commit bfa7362889) is just
>> that: describing when a subsection is needed. Forcing specific fields
>> to behave in a way consistent with QEMU 2.2 is bug compatibility.
>
> We do bug-compatible if it's not a big pain, too.
Where, in the specific case of migration?
Like Juan, I see where you're coming from. But it's a slippery slope,
and upstream chose not to go down it.
Paolo
next prev parent reply other threads:[~2015-06-17 11:33 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 18:54 [Qemu-devel] [PATCH] Migration compatibility for serial Dr. David Alan Gilbert (git)
2015-06-16 20:49 ` Michael S. Tsirkin
2015-06-17 9:09 ` Dr. David Alan Gilbert
2015-06-17 6:52 ` Markus Armbruster
2015-06-17 6:58 ` Michael S. Tsirkin
2015-06-17 7:11 ` Markus Armbruster
2015-06-17 7:25 ` Michael S. Tsirkin
2015-06-17 7:41 ` Paolo Bonzini
2015-06-17 7:52 ` Michael S. Tsirkin
2015-06-17 8:11 ` Paolo Bonzini
2015-06-17 10:13 ` Michael S. Tsirkin
2015-06-17 10:48 ` Juan Quintela
2015-06-17 10:51 ` Dr. David Alan Gilbert
2015-06-17 10:56 ` Michael S. Tsirkin
2015-06-17 10:59 ` Dr. David Alan Gilbert
2015-06-17 11:36 ` Michael S. Tsirkin
2015-06-17 10:55 ` Michael S. Tsirkin
2015-06-17 11:33 ` Paolo Bonzini [this message]
2015-06-17 11:40 ` Dr. David Alan Gilbert
2015-06-17 11:44 ` Paolo Bonzini
2015-06-17 11:48 ` Michael S. Tsirkin
2015-06-17 12:07 ` Dr. David Alan Gilbert
2015-06-17 12:20 ` Paolo Bonzini
2015-06-17 14:44 ` Michael S. Tsirkin
2015-06-17 16:34 ` Juan Quintela
2015-06-17 16:39 ` Michael S. Tsirkin
2015-06-17 16:40 ` Paolo Bonzini
2015-06-17 11:45 ` Michael S. Tsirkin
2015-06-17 11:53 ` Paolo Bonzini
2015-06-17 11:54 ` Michael S. Tsirkin
2015-06-17 11:55 ` Paolo Bonzini
2015-06-17 11:58 ` Michael S. Tsirkin
2015-06-17 12:20 ` Paolo Bonzini
2015-06-17 14:50 ` Michael S. Tsirkin
2015-06-17 16:16 ` Paolo Bonzini
2015-06-17 16:34 ` Michael S. Tsirkin
2015-06-17 16:35 ` Paolo Bonzini
2015-06-17 9:26 ` Juan Quintela
2015-06-17 10:37 ` Michael S. Tsirkin
2015-06-17 8:37 ` Dr. David Alan Gilbert
2015-06-17 8:49 ` Paolo Bonzini
2015-06-17 9:38 ` Dr. David Alan Gilbert
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=55815B06.5030508@redhat.com \
--to=pbonzini@redhat.com \
--cc=amit.shah@redhat.com \
--cc=dgilbert@redhat.com \
--cc=mst@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).