From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Cc: Aurelien Jarno <aurelien@aurel32.net>, Milton Miller <miltonm@bga.com>
Subject: Re: [Qemu-devel] I got a kernel booted under qemu-system-ppc !
Date: Sat, 20 Oct 2007 10:50:52 +0200 [thread overview]
Message-ID: <1192870252.16781.22.camel@rapid> (raw)
In-Reply-To: <200710200108.21660.rob@landley.net>
On Sat, 2007-10-20 at 01:08 -0500, Rob Landley wrote:
> On Friday 19 October 2007 3:33:52 pm Aurelien Jarno wrote:
> > Aurelien Jarno a écrit :
> > > - The target CPU never gets into idle loop, so the host CPU is always
> > > used at 100%
> >
> > This is actually not a problem. The default CPU (604) does not support
> > DOZE or NAP. Switching to a 603 CPU, the target CPU correctly goes
> > into idle loop.
Sleep mode is currently implemented only for a few CPUs. I should add
all the currently emulated cores. For this, I would have to emulate the
HID registers, in most case, which is still not done.
> This would be adding "-cpu 603" to the command line?
Yes
>
> Is there a web page listing all the powerpc processors somewhere? I'm still
> at the "everything is 7xx except for 4xx and 8xx" stage...
>
> I found this:
> http://www.power.org/resources/devcorner/roadmap
>
> But it groups by manufacturer rather than capabilities or software
> compatability...
I could do this, as Qemu has definitions for most PowerPC cores (even if
most are still not available).
For now, you can take a look in target-ppc/translate_init.c. Most
PowerPC are referenced here:
- there's a big table with all the PVR I know (but there's still a lot
missing)
- the ppc_defs table contains most PowerPC definitions, with their
features defined.
I will think of doing a reference table on my web pages, to have a more
readable PowerPC reference document. Of course, any information about
missing PVRs or PowerPC implementation in welcome !
You can also take a look at the file target-ppc/STATUS file to figure
out all cores emulation working in Qemu.
And you can get the list of all CPUs emulated by Qemu with the '-cpu ?'
switch.
--
J. Mayer <l_indien@magic.fr>
Never organized
next prev parent reply other threads:[~2007-10-20 8:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-19 0:12 [Qemu-devel] I got a kernel booted under qemu-system-ppc ! Rob Landley
2007-10-18 23:46 ` J. Mayer
2007-10-19 17:57 ` Milton Miller
2007-10-23 9:17 ` J. Mayer
2007-10-19 6:00 ` [Qemu-devel] " Milton Miller
2007-10-19 15:03 ` [Qemu-devel] " Aurelien Jarno
2007-10-19 15:19 ` Aurelien Jarno
2007-10-19 17:39 ` Jocelyn Mayer
2007-10-19 18:10 ` Milton Miller
2007-10-19 19:39 ` Aurelien Jarno
2007-10-19 20:33 ` Aurelien Jarno
2007-10-20 6:08 ` Rob Landley
2007-10-20 8:50 ` J. Mayer [this message]
2007-10-21 9:55 ` Rob Landley
2007-10-21 10:24 ` J. Mayer
2007-10-21 12:28 ` J. Mayer
2007-10-21 22:37 ` Rob Landley
2007-10-20 14:23 ` Aurelien Jarno
2007-10-20 14:49 ` Aurelien Jarno
2007-10-20 21:49 ` Aurelien Jarno
2007-10-21 9:01 ` J. Mayer
2007-10-20 7:52 ` Rob Landley
2007-10-20 9:03 ` J. Mayer
2007-10-20 9:42 ` Aurelien Jarno
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=1192870252.16781.22.camel@rapid \
--to=l_indien@magic.fr \
--cc=aurelien@aurel32.net \
--cc=miltonm@bga.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).