From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:35308) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SSO7m-0002Yc-Kw for qemu-devel@nongnu.org; Thu, 10 May 2012 03:49:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SSO7l-0004mp-1L for qemu-devel@nongnu.org; Thu, 10 May 2012 03:49:22 -0400 Received: from mx1.redhat.com ([209.132.183.28]:37437) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SSO7k-0004lx-Oo for qemu-devel@nongnu.org; Thu, 10 May 2012 03:49:20 -0400 Message-ID: <4FAB72F6.3070109@redhat.com> Date: Thu, 10 May 2012 09:49:10 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <4FAAA13E.10308@msgid.tls.msk.ru> <4FAB6E93.5050009@redhat.com> <4FAB726E.3030204@msgid.tls.msk.ru> In-Reply-To: <4FAB726E.3030204@msgid.tls.msk.ru> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] default qemu64 &Co CPUs makes no sense? List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Michael Tokarev Cc: Igor Mammedov , Eduardo Habkost , qemu-devel , =?UTF-8?B?QW5kcmVhcyBGw6RyYmVy?= , Julien Cristau Il 10/05/2012 09:46, Michael Tokarev ha scritto: >>> >> And in case kvm is enabled, and we run on some other CPU >>> >> (not intel and not amd), we'll have some other CPU model, >>> >> which might exist or might not, which may make some sense >>> >> or may not, etc - we simple don't know. >> > >> > Leaving aside the discussions on TCG, yes, this makes no sense for kvm. >> > You should use kvm32 and kvm64 instead. > In that case the question turns into a different one: why qemu64 > is default with -enable-kvm? Either way it makes no sense at all, > and that's whole my point. Yes, perhaps that can be changed. It's not trivial due to backwards-compatibility (need to keep -cpu qemu64 for versioned machine types <= 1.1), but doable. Paolo