qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: 440 emulation?
Date: Mon, 16 Mar 2009 15:00:27 -0500	[thread overview]
Message-ID: <1237233627.3591.45.camel@slate.austin.ibm.com> (raw)
In-Reply-To: <200903161441.29554.rob@landley.net>

On Mon, 2009-03-16 at 14:41 -0500, Rob Landley wrote:
> On Monday 16 March 2009 14:15:06 Hollis Blanchard wrote:
> > On Mon, 2009-03-16 at 14:05 -0500, Rob Landley wrote:
> > > I'm trying to come up with a working 440 toolchain and root filesystem,
> > > and I think I've built one (--with-cpu=440 for the binutils and gcc
> > > config seems to be the magic), but my attempt to test it under qemu with
> > > -M bamboo led to an "Unable to initialize CPU" message, because
> > > apparently the 440 isn't actually supported.
> >
> > Correct, 440 is not supported by TCG, so I'm not sure what you're trying
> > to do?
> 
> Test a 440 toolchain on an emulated bamboo board.  I discovered that it wasn't 
> supported when I got the "Unable to initialize CPU" message, and investigated.  
> I was hoping that either another processor could run 440 code (ala armv5 
> running armv4 code), or that 440 support was pending and simply hadn't been 
> merged yet.  Couldn't find anything about it in the archives, so I asked.  
> (Not particularly coherently, as it turns out.)

While Power Architecture allows you to run userspace code across
different cores, the same is not true for supervisor code.

As far as I know, nobody is working on 440 TCG emulation. I think the
most difficult part would be the new MMU model; there are some other
changes relative to 405 but I think they're pretty simple.

> > > I tried feeding in "-cpu 405" in hopes of getting something to at least
> > > launch (that's what the source code does when it's using kvm, anyway),
> > > but it still said it couldn't initialize the cpu.
> >
> > As you can see from quick inspection, none of the code involved pays any
> > attention to your -cpu option. If you want to make that work, it should
> > simply be a matter of plumbing 'cpu_model' through ppc440ep_init().
> 
> I might take a stab at that...

As long as you know you're testing 405 support, not 440. If you build a
405 Linux kernel with device tree support, it might just work.

> > > Presumably this works for somebody, but I dunno how to get it to do
> > > anything interesting.  What is the status of the bamboo board?
> >
> > It works, as long as you can provide working core emulation.
> 
> I take it the only way to do this currently is to run kvm on actual 440 
> hardware?

Yes; KVM doesn't translate instruction sets.

(In theory you could do a little intra-architecture emulation to e.g.
run a 405 guest on 440 host, but this has not been implemented.)

-- 
Hollis Blanchard
IBM Linux Technology Center

      reply	other threads:[~2009-03-16 20:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 19:05 [Qemu-devel] 440 emulation? Rob Landley
2009-03-16 19:15 ` [Qemu-devel] " Hollis Blanchard
2009-03-16 19:41   ` Rob Landley
2009-03-16 20:00     ` Hollis Blanchard [this message]

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=1237233627.3591.45.camel@slate.austin.ibm.com \
    --to=hollisb@us.ibm.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).