From: john cooper <john.cooper@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Chris Wright <chrisw@sous-sol.org>,
"Przywara, Andre" <Andre.Przywara@amd.com>,
qemu-devel@nongnu.org, KVM list <kvm@vger.kernel.org>,
john.cooper@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Add definitions for current cpu models..
Date: Wed, 20 Jan 2010 15:09:53 -0500 [thread overview]
Message-ID: <4B576311.3030906@redhat.com> (raw)
In-Reply-To: <4B563144.9030803@codemonkey.ws>
Anthony Liguori 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.
$ grep name /proc/cpuinfo
model name : Intel(R) Core(TM)2 Duo CPU E8400 @ 3.00GHz
Which is detailing that exact cpu vs. the class
of which it is a member. So are you suggesting
to map all instances of processors called out
in /proc/cpuinfo into one of the three defined
models? We can certainly do that however I was
looking for a more terse and simplified solution
at this level while deferring more ornate mapping
schemes to management tools.
Still at the user facing CLI this doesn't strike
me as the most friendly encoding of a -cpu <name>.
-john
--
john.cooper@redhat.com
next prev parent reply other threads:[~2010-01-20 20:14 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
2010-01-20 14:27 ` Gleb Natapov
2010-01-20 1:38 ` Jamie Lokier
2010-01-20 20:09 ` john cooper [this message]
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=4B576311.3030906@redhat.com \
--to=john.cooper@redhat.com \
--cc=Andre.Przywara@amd.com \
--cc=anthony@codemonkey.ws \
--cc=chrisw@sous-sol.org \
--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).