qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PPC emulation on Qemu
Date: Mon, 16 Feb 2004 18:09:38 +1100	[thread overview]
Message-ID: <1076915377.6957.222.camel@gaston> (raw)
In-Reply-To: <1076905652.25228.2193.camel@rapid>


> > What is OpenPPC standard ? So far, the most "standard" PPCs are
> > PowerMacs ;) 
> 
> Well, G4 Macs are close to OpenPPC standard, which is an open platform
> which has been described by IBM. I like it has a reference because it's
> nearly Macs and because AIX, MacOS (X I suppose) and Linux should be
> able to run on it.

You mean CHRP ? Hrm... AIX ? hehe, I wouldn't bet on that :) OS X
neither. But at least for OS X, you can write your own drivers,
like MOL does.

> Yes I know it can run Linux, but what I wanted to point is that (if I'm
> not wrong) it's not able to run any OS (ie AIX or pegasos or, why not
> (?), BeOS or AmigaOS) like a real machine would.

It could. All depends on which HW you emulate.

> I agree that MOL exactly intend to do this, and does it well, but I
> think qemu should really emulate the whole execution environment...
> 
> Does the OSI calls mechanism needs patched OS and/or firmware ?

It's an addition. MOL can run without it, it's just an optimisation
so you can load special drivers into the host OS to makes things
much faster / more useable.

On MacOS, it makes a lot of sense since the drivers can be provided
by the bootloader at boot or even in the ROM of some PCI cards, so
MOL can transparently get those loaded into the host operating
system when it's MacOS 9 or X.

Also, for OS X, MOL actually loads a special kext that patches the
kernel to remove it's use of MMU split mode, which isn't necessary
under emulation and actually very slow to emulate.

Ben.

  reply	other threads:[~2004-02-16  7:12 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-15 11:17 [Qemu-devel] PPC emulation on Qemu Manish Bansal
2004-02-15 14:07 ` J. Mayer
2004-02-15 14:59   ` Gabriel Ebner
2004-02-15 16:06     ` J. Mayer
2004-02-15 22:44       ` Benjamin Herrenschmidt
2004-02-16  3:34         ` J. Mayer
2004-02-16  4:08           ` Benjamin Herrenschmidt
2004-02-16  4:27             ` J. Mayer
2004-02-16  7:09               ` Benjamin Herrenschmidt [this message]
2004-02-18  9:42                 ` J. Mayer
2004-02-18 10:35                   ` J. Fortmann
2004-02-18 13:20                     ` Jocelyn Mayer
2004-02-18 23:13                       ` Benjamin Herrenschmidt
2004-02-19  0:59                         ` J. Mayer
2004-02-19  1:57                           ` Benjamin Herrenschmidt
2004-02-19  2:32                             ` J. Mayer
2004-02-19  2:48                               ` Benjamin Herrenschmidt
2004-02-19  3:33                                 ` J. Mayer
2004-02-19  4:27                                   ` Benjamin Herrenschmidt
2004-02-16  7:20               ` Gwenole Beauchesne
2004-02-16  7:46                 ` Chad Page

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=1076915377.6957.222.camel@gaston \
    --to=benh@kernel.crashing.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).