From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40036) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7Vtu-0005S7-KF for qemu-devel@nongnu.org; Tue, 23 Jun 2015 17:38:39 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z7Vtr-000814-AK for qemu-devel@nongnu.org; Tue, 23 Jun 2015 17:38:38 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48504) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7Vtr-000810-4m for qemu-devel@nongnu.org; Tue, 23 Jun 2015 17:38:35 -0400 Date: Tue, 23 Jun 2015 23:38:30 +0200 From: "Michael S. Tsirkin" Message-ID: <20150623233555-mutt-send-email-mst@redhat.com> References: <20150623183115-mutt-send-email-mst@redhat.com> <20150623163858.GG3134@thinpad.lan.raisama.net> <55898D09.2060405@suse.de> <20150623170859.GH3134@thinpad.lan.raisama.net> <558994CE.9050001@suse.de> <20150623173917.GK3134@thinpad.lan.raisama.net> <5589A70A.9050201@suse.de> <20150623192544.GO3134@thinpad.lan.raisama.net> <5589B67F.5090409@suse.de> <20150623202638.GQ3134@thinpad.lan.raisama.net> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20150623202638.GQ3134@thinpad.lan.raisama.net> Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH 0/2] target-i386: "custom" CPU model + script to dump existing CPU models List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eduardo Habkost Cc: Peter Maydell , mimu@linux.vnet.ibm.com, qemu-devel@nongnu.org, Alexander Graf , borntraeger@de.ibm.com, Igor Mammedov , Paolo Bonzini , Jiri Denemark , Andreas =?iso-8859-1?Q?F=E4rber?= , rth@twiddle.net On Tue, Jun 23, 2015 at 05:26:38PM -0300, Eduardo Habkost wrote: > On Tue, Jun 23, 2015 at 09:41:51PM +0200, Andreas F=E4rber wrote: > [...] > > Given that we have had this versioning system for years and no proble= m > > specifically with 2.4 has been raised, I see this as 2.5+ material at > > this point. >=20 > I see this on 2.4 schedule: >=20 > "2015-06-16 Soft feature freeze. All features > should have patches on the list by this date; major features should ha= ve > initial code committed." >=20 > It is a 9-line patch (from which 6 are declarations, and 2 are actual > code statements), it doesn't affect anybody who is not explicitly using > "-cpu custom", it is an useful feature, and it has been on the list > since June 8 (and as RFC since April 13). >=20 > Unless somebody gives me a good reason to consider it harmful (that's > different from not accepting the explanations why it is useful, or > disagreeing with users that want to use it), I would like to include it > in 2.4 as long as I get Reviewed-by lines before hard freeze. For the record I have nothing against the patch itself. Might be useful for testing or something. And how libvirt uses QEMU is, in the end, in the hands of libvirt developers. I do care about command line stability generally, and about people not breaking existing documentation and tools using QEMU directly as opposed to through libvirt, that's the only reason I participated in this discussion. > --=20 > Eduardo