From: Amit Shah <amit.shah@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] Add phenom CPU descriptor
Date: Fri, 30 Jan 2009 14:36:52 +0530 [thread overview]
Message-ID: <20090130090652.GA25998@amit-x200.pnq.redhat.com> (raw)
In-Reply-To: <200901272256.41247.paul@codesourcery.com>
On (Tue) Jan 27 2009 [22:56:40], Paul Brook wrote:
> > > Although this is a bit different. We aren't actually emulating a
> > > phenom. We're just taking what we have and calling it a phenom. I
> > > suspect there's going to be a desire to call whatever we emulate
> > > arbitrary things.
> >
> > I don't think we're likely to want the big list of cpus anyway.
>
> Argh. I got that completely wrong.I mean we *are* likely to want a big list of
> cpus anyway. If done properly it should be fairly easy to maintain.
> e.g. instead of missing out unimplemented feature flags in each cpu, add them
> all, then have qemu mask out the ones it doesn't implement.
What I'm thinking of is moving all the CPU definitions out from helper.c
into $(PREFIX)/usr/share/qemu/cpu-defs/... with one file holding one
definition, like
$ cat core2duo.def
model= 15
family = 16
stepping = 11
level = 10
.
.
.
Adding a new def then just becomes a matter of submitting a text file
for inclusion and doesn't need any recompilation.
Also, there are many details not captured in a CPU def, like the cache
sizes and types. They're hard-coded for all the CPUs in the cpuid helper
function. So we could have those values too incorporated in the CPU def
file an fall back to the defaults when not available.
When we do get some kind of a machine FDT, we can specify the cpu type
by either pointing to one of these files or by constructing a new CPU
type by specifying individual values.
Amit
next prev parent reply other threads:[~2009-01-30 9:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 12:35 [Qemu-devel] [PATCH 0/2] Add Phenom CPU Descriptor Alexander Graf
2009-01-27 12:35 ` [Qemu-devel] [PATCH 1/2] Implement FFXSR Alexander Graf
2009-01-27 12:35 ` [Qemu-devel] [PATCH 2/2] Add phenom CPU descriptor Alexander Graf
2009-01-27 14:37 ` Anthony Liguori
2009-01-27 15:16 ` Alexander Graf
2009-01-27 15:33 ` Laurent Vivier
2009-01-27 19:12 ` Anthony Liguori
2009-01-27 22:39 ` Paul Brook
2009-01-27 22:56 ` Paul Brook
2009-01-28 16:43 ` Jamie Lokier
2009-01-30 9:06 ` Amit Shah [this message]
2009-01-28 8:17 ` Alexander Graf
2009-02-02 17:11 ` [Qemu-devel] [PATCH 0/2] Add Phenom CPU Descriptor Anthony Liguori
-- strict thread matches above, loose matches on Subject: below --
2009-01-05 16:11 [Qemu-devel] [PATCH 0/2] VMware ESX guest bringup (partial) Alexander Graf
2009-01-05 16:11 ` [Qemu-devel] [PATCH 1/2] [RFC] Make vmport report the processor speed Alexander Graf
2009-01-05 16:11 ` [Qemu-devel] [PATCH 2/2] Add phenom CPU descriptor Alexander Graf
2009-01-09 23:16 ` Alexander Graf
2009-01-09 23:36 ` Anthony Liguori
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=20090130090652.GA25998@amit-x200.pnq.redhat.com \
--to=amit.shah@redhat.com \
--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).