From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56157) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZaU3w-000840-Tz for qemu-devel@nongnu.org; Fri, 11 Sep 2015 15:32:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZaU3r-0001eH-Tk for qemu-devel@nongnu.org; Fri, 11 Sep 2015 15:32:44 -0400 Received: from mail-qk0-x236.google.com ([2607:f8b0:400d:c09::236]:35625) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZaU3r-0001dq-Ow for qemu-devel@nongnu.org; Fri, 11 Sep 2015 15:32:39 -0400 Received: by qkap81 with SMTP id p81so36364394qka.2 for ; Fri, 11 Sep 2015 12:32:38 -0700 (PDT) Sender: Richard Henderson References: <1441999509-26881-1-git-send-email-ehabkost@redhat.com> From: Richard Henderson Message-ID: <55F32C53.8050606@twiddle.net> Date: Fri, 11 Sep 2015 12:32:35 -0700 MIME-Version: 1.0 In-Reply-To: <1441999509-26881-1-git-send-email-ehabkost@redhat.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 0/4] target-i386: Don't try to enable unsupported TCG features by default List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eduardo Habkost , qemu-devel@nongnu.org Cc: Igor Mammedov , =?UTF-8?Q?Andreas_F=c3=a4rber?= , Paolo Bonzini On 09/11/2015 12:25 PM, Eduardo Habkost wrote: > This series makes QEMU stop trying to enable an unsupported feature by default > in TCG mode, avoiding the warnings shown by the (now enabled by default) > "check" mode. > > To do that, I cchanged the kvm_default_features code to be based on QOM > properties, and added a new "type" field to allow per-CPU-model KVM defaults to > be specified. > > Before this series: > > $ qemu-system-x86_64 -S > warning: TCG doesn't support requested feature: CPUID.01H:EDX.de [bit 2] > warning: TCG doesn't support requested feature: CPUID.80000001H:EDX [bit 2] > > After this series: > > $ ./x86_64-softmmu/qemu-system-x86_64 -S > [no warning output] Wouldn't it be easier simply to implement this bit? It seems like we're simply creating a compatibility mess otherwise. r~