From: john cooper <john.cooper@redhat.com>
To: Jamie Lokier <jamie@shareable.org>
Cc: 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: Thu, 21 Jan 2010 13:36:21 -0500 [thread overview]
Message-ID: <4B589EA5.2020501@redhat.com> (raw)
In-Reply-To: <20100121181300.GC28467@shareable.org>
Jamie Lokier wrote:
> I think we can all agree that there is no point looking for a familiar
> -cpu naming scheme because there aren't any familiar and meaningful names
> these days.
Even if we dismiss the Intel coined names as internal
code names, there is still VMW's use of them in this
space which we can either align with or attempt to
displace. All considered I don't see any motivation
nor gain in doing the latter. Anyway it doesn't appear
likely we're going to resolve this to our collective
satisfaction with a hard-wired naming scheme.
> It would be nice if qemu could tell the user which of the built-in
> -cpu choices is the most featureful subset of their own host. With
> -cpu host implemented, finding that is probably quite easy.
This should be doable although it may not be as simple
as traversing a hierarchy of features and picking one
with the most host flags present. In any case this
should be fairly detachable from settling the immediate
issue.
-john
--
john.cooper@redhat.com
next prev parent reply other threads:[~2010-01-21 18:40 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
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 [this message]
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=4B589EA5.2020501@redhat.com \
--to=john.cooper@redhat.com \
--cc=Andre.Przywara@amd.com \
--cc=jamie@shareable.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).