From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NST4t-0003nr-0X for qemu-devel@nongnu.org; Wed, 06 Jan 2010 05:25:23 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NST4p-0003mR-31 for qemu-devel@nongnu.org; Wed, 06 Jan 2010 05:25:22 -0500 Received: from [199.232.76.173] (port=57358 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NST4o-0003mL-M5 for qemu-devel@nongnu.org; Wed, 06 Jan 2010 05:25:18 -0500 Received: from mx1.redhat.com ([209.132.183.28]:48252) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NST4o-0001Yp-6q for qemu-devel@nongnu.org; Wed, 06 Jan 2010 05:25:18 -0500 Message-ID: <4B44650A.3000008@redhat.com> Date: Wed, 06 Jan 2010 12:25:14 +0200 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] cpuid problem in upstream qemu with kvm 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> <20100106102129.GC28824@redhat.com> In-Reply-To: <20100106102129.GC28824@redhat.com> 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: "Daniel P. Berrange" Cc: Gleb Natapov , "Michael S. Tsirkin" , John Cooper , dlaor@redhat.com, qemu-devel@nongnu.org, Alexander Graf On 01/06/2010 12:21 PM, Daniel P. Berrange wrote: > 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 > Yes, that's what I'm thinking of. Along with enumerating all the other qemu capabilities. -- error compiling committee.c: too many arguments to function