From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57335) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7STC-0005WL-0A for qemu-devel@nongnu.org; Tue, 23 Jun 2015 13:58:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z7ST7-00026c-SK for qemu-devel@nongnu.org; Tue, 23 Jun 2015 13:58:49 -0400 Received: from cantor2.suse.de ([195.135.220.15]:40414 helo=mx2.suse.de) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7ST7-00026N-NH for qemu-devel@nongnu.org; Tue, 23 Jun 2015 13:58:45 -0400 Message-ID: <55899E54.3040403@suse.de> Date: Tue, 23 Jun 2015 19:58:44 +0200 From: =?windows-1252?Q?Andreas_F=E4rber?= MIME-Version: 1.0 References: <20150623155832.GE3134@thinpad.lan.raisama.net> <55898637.6080804@suse.de> <20150623162555.GL30318@redhat.com> <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> <20150623172750.GP30318@redhat.com> <55899A5E.3060509@suse.de> <20150623174520.GM3134@thinpad.lan.raisama.net> In-Reply-To: <20150623174520.GM3134@thinpad.lan.raisama.net> Content-Type: text/plain; charset=windows-1252 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: mimu@linux.vnet.ibm.com, "Michael S. Tsirkin" , qemu-devel@nongnu.org, Alexander Graf , borntraeger@de.ibm.com, Igor Mammedov , Paolo Bonzini , Jiri Denemark , rth@twiddle.net Am 23.06.2015 um 19:45 schrieb Eduardo Habkost: > On Tue, Jun 23, 2015 at 07:41:50PM +0200, Andreas F=E4rber wrote: > [...] >> If that is the whole problem here, then why not just add a global flag >> to only enable explicitly requested KVM features? All other features >> should not depend on the host, and the whole discussion about -x.y see= ms >> like a distraction. >=20 > Now replace "KVM features" with "CPU fatures", because all CPU features > are KVM features, as all of them depend on KVM code enabling them on > GET_SUPPORTED_CPUID. >=20 > Thus, the global flag to only enable explicitly request KVM features on > CPUs is "-cpu custom", which doesn't enable any CPU feature at all. If libvirt wants to use an empty CPU model, then why export our models to libvirt? I don't mind there being an optional custom model, I mind our compat_props getting ignored that way, which are unrelated to adding new features, in fact they suppress just that for the -2.3 examples. Andreas --=20 SUSE Linux GmbH, Maxfeldstr. 5, 90409 N=FCrnberg, Germany GF: Felix Imend=F6rffer, Jane Smithard, Dilip Upmanyu, Graham Norton; HRB 21284 (AG N=FCrnberg)