From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NSXZ5-0003B4-4g
	for qemu-devel@nongnu.org; Wed, 06 Jan 2010 10:12:51 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NSXZ0-00039G-Jf
	for qemu-devel@nongnu.org; Wed, 06 Jan 2010 10:12:50 -0500
Received: from [199.232.76.173] (port=44169 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NSXZ0-00039C-Go
	for qemu-devel@nongnu.org; Wed, 06 Jan 2010 10:12:46 -0500
Received: from mail-bw0-f212.google.com ([209.85.218.212]:38639)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1NSXZ0-0002AV-2f
	for qemu-devel@nongnu.org; Wed, 06 Jan 2010 10:12:46 -0500
Received: by bwz4 with SMTP id 4so10882520bwz.2
	for <qemu-devel@nongnu.org>; Wed, 06 Jan 2010 07:12:43 -0800 (PST)
Message-ID: <4B44A864.9010404@codemonkey.ws>
Date: Wed, 06 Jan 2010 09:12:36 -0600
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] cpuid problem in upstream qemu with kvm
References: <4B2DF334.6030208@redhat.com>
	<20091220155101.GB31257@redhat.com>	<4B2E49E5.6050709@redhat.com>
	<20091220165612.GC31257@redhat.com>	<C9DA6F14-719C-49C2-A9B5-C74A64603026@suse.de>	<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>
	<4B4402B1.1030605@redhat.com> <4B448F36.8030605@codemonkey.ws>
	<4B449467.4070606@redhat.com> <4B4494FC.1080907@codemonkey.ws>
	<4B449608.7040102@redhat.com>
In-Reply-To: <4B449608.7040102@redhat.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Avi Kivity <avi@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>, John Cooper <john.cooper@redhat.com>, dlaor@redhat.com, qemu-devel@nongnu.org, Alexander Graf <agraf@suse.de>

On 01/06/2010 07:54 AM, Avi Kivity wrote:
> On 01/06/2010 03:49 PM, Anthony Liguori wrote:
>>>
>>>>
>>>> I think that's workable but I think there may be some subtle issues 
>>>> especially across qemu versions.  Can you give an example of what 
>>>> you would expect the output to be?
>>>
>>> -> { command: query-cpu-capabalities }
>>> <- { result: { features: [vm, fpu, lm, sse2, sse3, sssse3, 
>>> ssssssse3, sse3.14 ], cache: { ... }, vendor: { .... }, etc. } }
>>>
>>> Or something.  We'd need similar queries for the number of PCI 
>>> slots, for example, so the GUI can tell the user when adding 
>>> hardware is no longer an option instead of trying it blindly and 
>>> returning an error.
>>
>>
>> Yeah, the trick with this is that we don't have such a thing as a 
>> bare bones CPU in qemu right now.
>>
>> So you can't really say -cpu qemu64+vm+fpu+lm....
>>
>> Because some extra features might sneak in.  What I'm getting at is 
>> that we need a way to make the results of this command translate into 
>> a -cpu invocation that works reliably across multiple versions of qemu.
>
> Well, we can freeze qemu64 if we wish.  That's still not 100% accurate 
> since kvm can remove features from qemu64.
>
> -cpu none,+flags,vendor=foo,cache=bar,ad=nauseum?

Yeah, I'm not sure I can think of a better way.

Regards,

Anthony Liguori