From: Anthony Liguori <anthony@codemonkey.ws>
To: Chris Wright <chrisw@sous-sol.org>
Cc: john cooper <john.cooper@redhat.com>,
"Przywara, Andre" <Andre.Przywara@amd.com>,
qemu-devel@nongnu.org, KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH] Add definitions for current cpu models..
Date: Wed, 20 Jan 2010 08:21:44 -0600 [thread overview]
Message-ID: <4B571178.5040409@codemonkey.ws> (raw)
In-Reply-To: <20100120001501.GJ3204@sequoia.sous-sol.org>
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
next prev parent reply other threads:[~2010-01-20 14:21 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-18 16:45 [Qemu-devel] [PATCH] Add definitions for current cpu models john cooper
2010-01-19 19:39 ` Anthony Liguori
2010-01-19 20:03 ` Chris Wright
2010-01-19 22:12 ` Jamie Lokier
2010-01-19 22:20 ` Chris Wright
2010-01-19 22:25 ` Anthony Liguori
2010-01-20 0:15 ` Chris Wright
2010-01-20 14:21 ` Anthony Liguori [this message]
2010-01-20 14:27 ` Gleb Natapov
2010-01-20 1:38 ` Jamie Lokier
2010-01-20 20:09 ` john cooper
2010-01-20 20:26 ` Daniel P. Berrange
2010-01-20 20:53 ` Anthony Liguori
2010-01-21 0:25 ` Chris Wright
2010-01-21 1:18 ` john cooper
2010-01-21 14:39 ` Andre Przywara
2010-01-21 17:06 ` Blue Swirl
2010-01-21 15:05 ` Anthony Liguori
2010-01-21 16:43 ` john cooper
2010-01-21 18:59 ` Anthony Liguori
2010-01-25 9:08 ` Dor Laor
2010-01-25 11:27 ` Jamie Lokier
2010-01-25 14:21 ` Anthony Liguori
2010-01-25 22:35 ` Dor Laor
2010-01-26 8:26 ` Gerd Hoffmann
2010-01-26 12:54 ` Anthony Liguori
2010-01-28 8:19 ` Arnd Bergmann
2010-01-28 8:43 ` Alexander Graf
2010-01-28 10:09 ` Arnd Bergmann
2010-01-28 14:10 ` Anthony Liguori
2010-01-19 22:11 ` Jamie Lokier
2010-01-20 20:09 ` john cooper
2010-01-21 17:50 ` Jamie Lokier
2010-01-21 18:13 ` Jamie Lokier
2010-01-21 18:36 ` john cooper
2010-01-19 22:15 ` Jamie Lokier
2010-01-20 20:11 ` john cooper
2010-01-21 17:55 ` Jamie Lokier
2010-01-21 18:34 ` john cooper
2010-01-20 23:20 ` [Qemu-devel] " Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2009-12-21 6:46 [Qemu-devel] " john cooper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B571178.5040409@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=Andre.Przywara@amd.com \
--cc=chrisw@sous-sol.org \
--cc=john.cooper@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).