From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NXbWi-0001WF-24 for qemu-devel@nongnu.org; Wed, 20 Jan 2010 09:27:20 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NXbWd-0001TH-BH for qemu-devel@nongnu.org; Wed, 20 Jan 2010 09:27:19 -0500 Received: from [199.232.76.173] (port=58345 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NXbWd-0001TB-65 for qemu-devel@nongnu.org; Wed, 20 Jan 2010 09:27:15 -0500 Received: from mx1.redhat.com ([209.132.183.28]:32221) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NXbWc-0005xu-Ku for qemu-devel@nongnu.org; Wed, 20 Jan 2010 09:27:14 -0500 Date: Wed, 20 Jan 2010 16:27:08 +0200 From: Gleb Natapov Subject: Re: [Qemu-devel] [PATCH] Add definitions for current cpu models.. Message-ID: <20100120142708.GL5238@redhat.com> References: <4B549016.6090501@redhat.com> <4B560A88.9@codemonkey.ws> <20100119200349.GG3204@sequoia.sous-sol.org> <4B563144.9030803@codemonkey.ws> <20100120001501.GJ3204@sequoia.sous-sol.org> <4B571178.5040409@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B571178.5040409@codemonkey.ws> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Chris Wright , john cooper , qemu-devel@nongnu.org, KVM list , "Przywara, Andre" On Wed, Jan 20, 2010 at 08:21:44AM -0600, Anthony Liguori wrote: > On 01/19/2010 06:15 PM, Chris Wright wrote: > >* Anthony Liguori (anthony@codemonkey.ws) wrote: > >>On 01/19/2010 02:03 PM, Chris Wright wrote: > >>>* Anthony Liguori (anthony@codemonkey.ws) wrote: > >>> > >>>>I'm very much against having -cpu Nehalem. The whole point of this is > >>>>to make things easier for a user and for most of the users I've > >>>>encountered, -cpu Nehalem is just as obscure as -cpu > >>>>qemu64,-sse3,+vmx,... > >>>> > >>>What name will these users know? FWIW, it makes sense to me as it is. > >>Whatever is in /proc/cpuinfo. > >That doesn't exactly generalize to families w/ similar cpuid features. > > > >Intel(R) Xeon(R) {E,L,X}{74,55}** > >Intel(R) Core(TM)2 {Duo,Quad,Extreme} ... > > Then we should key off of family and model. > > So -cpu AMD_Family_10h > > or something like that. At least that is discoverable by a user. > Or use CPU price/year as a distinguisher. -cpu Intel_300$_2005 will give you Intel cpus that cost 300$ in 2005. -- Gleb.