From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NSYbq-0005V5-Fu for qemu-devel@nongnu.org; Wed, 06 Jan 2010 11:19:46 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NSYbm-0005TN-Sy for qemu-devel@nongnu.org; Wed, 06 Jan 2010 11:19:46 -0500 Received: from [199.232.76.173] (port=50415 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NSYbm-0005TI-Im for qemu-devel@nongnu.org; Wed, 06 Jan 2010 11:19:42 -0500 Received: from caffeine.csclub.uwaterloo.ca ([129.97.134.17]:35725) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NSYbl-0005OY-Kd for qemu-devel@nongnu.org; Wed, 06 Jan 2010 11:19:42 -0500 Date: Wed, 6 Jan 2010 11:19:35 -0500 Subject: Re: [Qemu-devel] cpuid problem in upstream qemu with kvm Message-ID: <20100106161935.GS8605@caffeine.csclub.uwaterloo.ca> References: <20091220171822.GD31257@redhat.com> <20091220172341.GB21163@redhat.com> <2162E312-0110-42E1-A391-D75A6F013554@suse.de> <20091220173702.GC21163@redhat.com> <4B2E660F.1050703@codemonkey.ws> <20091221074355.GU4490@redhat.com> <4B2F31B1.6040403@redhat.com> <4B30EFDF.4060202@codemonkey.ws> <4B31F1BA.10005@redhat.com> <4B43D4E2.9050102@codemonkey.ws> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B43D4E2.9050102@codemonkey.ws> From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen) List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Gleb Natapov , "Michael S. Tsirkin" , John Cooper , dlaor@redhat.com, qemu-devel@nongnu.org, Alexander Graf , Avi Kivity On Tue, Jan 05, 2010 at 06:10:10PM -0600, Anthony Liguori wrote: > Typically, there is at least a little sanity naming for these cases. > For instance, any Xeon W35xx should have the same features. A Xeon > W55xx may be different. It doesn't work that way for intel. For example: Core 2 Duo E7400 AT80571PH0723M does not have VT support. Core 2 Duo E7400 AT80571PH0723ML does have VT support. Good luck buying the variant you want. So model names do not define the feature set. > It's not going to be easy to include every possible model. It's a hard > problem for management tools too. The thing is, I imagine most > management tools are going to cat /proc/cpuinfo to get what the > processor is and that's going to be a Xeon YYXXXX type name so I really > believe that's the thing that makes sense to expose in QEMU. > > Maybe we could name models like IntelXeonW35xx. > > Clever use of the preprocessor will make this effort much, much saner. > Also, we really need some sort of human readable document that explains > the differences between processor classes and makes recommendations > about what management tools should take into consideration. -- Len Sorensen