From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NXbRS-0007JS-NZ for qemu-devel@nongnu.org; Wed, 20 Jan 2010 09:21:54 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NXbRO-0007I0-OD for qemu-devel@nongnu.org; Wed, 20 Jan 2010 09:21:54 -0500 Received: from [199.232.76.173] (port=56034 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NXbRO-0007Hs-IB for qemu-devel@nongnu.org; Wed, 20 Jan 2010 09:21:50 -0500 Received: from mail-qy0-f199.google.com ([209.85.221.199]:44784) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NXbRO-0005D9-Ad for qemu-devel@nongnu.org; Wed, 20 Jan 2010 09:21:50 -0500 Received: by qyk37 with SMTP id 37so2886371qyk.18 for ; Wed, 20 Jan 2010 06:21:47 -0800 (PST) Message-ID: <4B571178.5040409@codemonkey.ws> Date: Wed, 20 Jan 2010 08:21:44 -0600 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH] Add definitions for current cpu models.. 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> In-Reply-To: <20100120001501.GJ3204@sequoia.sous-sol.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Chris Wright Cc: john cooper , "Przywara, Andre" , qemu-devel@nongnu.org, KVM list 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. Regards, Anthony Liguori