From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NST1I-0000yL-0J for qemu-devel@nongnu.org; Wed, 06 Jan 2010 05:21:40 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NST1C-0000ph-Sh for qemu-devel@nongnu.org; Wed, 06 Jan 2010 05:21:39 -0500 Received: from [199.232.76.173] (port=36530 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NST1C-0000pN-Mk for qemu-devel@nongnu.org; Wed, 06 Jan 2010 05:21:34 -0500 Received: from mx1.redhat.com ([209.132.183.28]:27308) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NST1C-0000Da-BI for qemu-devel@nongnu.org; Wed, 06 Jan 2010 05:21:34 -0500 Date: Wed, 6 Jan 2010 10:21:29 +0000 From: "Daniel P. Berrange" Subject: Re: [Qemu-devel] cpuid problem in upstream qemu with kvm Message-ID: <20100106102129.GC28824@redhat.com> References: <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> <20100106094414.GA28824@redhat.com> <4B445DC8.4080509@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B445DC8.4080509@redhat.com> Reply-To: "Daniel P. Berrange" List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Gleb Natapov , "Michael S. Tsirkin" , John Cooper , dlaor@redhat.com, qemu-devel@nongnu.org, Alexander Graf On Wed, Jan 06, 2010 at 11:54:16AM +0200, Avi Kivity wrote: > On 01/06/2010 11:44 AM, Daniel P. Berrange wrote: > > > >This is all a very long way of saying that mgmt apps based on libvirt > >won't care about model names exposed in /proc/cpuinfo so there's no > >particular need to have a direct mapping from them to QEMU for libvirt's > >needs. > > > > There is still a need to query qemu, since it will filter out bits that > kvm.ko or the hardware don't support. If there was a more verbose version of '-cpu ?' which also gave the CPUID masks associated with each supported CPU model, that would be useful info avoiding need for libvirt to hardcode the mapping to QEMU Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|