From: Jamie Lokier <jamie@shareable.org>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Chris Wright <chrisw@sous-sol.org>,
john cooper <john.cooper@redhat.com>,
qemu-devel@nongnu.org, KVM list <kvm@vger.kernel.org>,
"Przywara, Andre" <Andre.Przywara@amd.com>
Subject: Re: [Qemu-devel] [PATCH] Add definitions for current cpu models..
Date: Wed, 20 Jan 2010 01:38:49 +0000 [thread overview]
Message-ID: <20100120013849.GE11920@shareable.org> (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.
>
> There is no mention of "Nehalem" in /proc/cpuinfo.
My 5 /proc/cpuinfos say:
Genuine Intel(R) CPU T2500 @ 2.00GHz
Intel(R) Xeon(TM) CPU 3.00GHz
Intel(R) Xeon(R) CPU E5335 @ 2.00GHz
Intel(R) Xeon(TM) CPU 2.80GHz
Intel(R) Xeon(R) CPU X5482 @ 3.20GHz
I'm not sure if that's any more helpful :-)
Especially the first one. I don't think of my laptop as having a
T2500. I think of it as having a 32-bit Core Duo. And I have no idea
what the different types of Xeon are. But then, I couldn't tell you
whether they are Nehalems or Penryns either, and I'm quite sure the
owners couldn't either.
$ grep name /proc/cpuinfo
model name : QEMU Virtual CPU version 0.9.1
If only they were all so clear :-)
-- Jamie
next prev parent reply other threads:[~2010-01-20 1:39 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 [this message]
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=20100120013849.GE11920@shareable.org \
--to=jamie@shareable.org \
--cc=Andre.Przywara@amd.com \
--cc=anthony@codemonkey.ws \
--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).