From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:58970) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z58S2-00006c-3H for qemu-devel@nongnu.org; Wed, 17 Jun 2015 04:12:07 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z58Rv-000219-Et for qemu-devel@nongnu.org; Wed, 17 Jun 2015 04:12:02 -0400 Received: from mail-wi0-x236.google.com ([2a00:1450:400c:c05::236]:35077) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z58Rv-00020n-7j for qemu-devel@nongnu.org; Wed, 17 Jun 2015 04:11:55 -0400 Received: by wiga1 with SMTP id a1so130961280wig.0 for ; Wed, 17 Jun 2015 01:11:54 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <55812BC4.3000600@redhat.com> Date: Wed, 17 Jun 2015 10:11:48 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1434480849-23093-1-git-send-email-dgilbert@redhat.com> <558124BD.8010807@redhat.com> <20150617094829-mutt-send-email-mst@redhat.com> In-Reply-To: <20150617094829-mutt-send-email-mst@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] Migration compatibility for serial List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Michael S. Tsirkin" Cc: amit.shah@redhat.com, qemu-devel@nongnu.org, "Dr. David Alan Gilbert (git)" , quintela@redhat.com 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. Paolo