From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Cc: oliver <oliver@linux-kernel.at>
Subject: Re: [Qemu-devel] qemu alpha?
Date: Sun, 21 Oct 2007 13:06:43 +0200 [thread overview]
Message-ID: <1192964804.16781.75.camel@rapid> (raw)
In-Reply-To: <200710210543.14960.rob@landley.net>
On Sun, 2007-10-21 at 05:43 -0500, Rob Landley wrote:
> On Saturday 20 October 2007 3:56:12 am J. Mayer wrote:
> > On Fri, 2007-10-19 at 19:49 -0500, Rob Landley wrote:
> > > On Sunday 14 October 2007 5:14:27 am J. Mayer wrote:
> > > > On Sun, 2007-10-14 at 11:19 +0200, Oliver Falk wrote:
> > > > > Hi list!
> > > >
> > > > Hi you !
> > > >
> > > > > Just wanted to know how far the progress on alpha target is? I would
> > > > > be happy if I have some 'virtual alpha' to test new isos.
> > > > >
> > > > > If I can help some way (I have a few alphas around). Let me know.
> > > >
> > > > I'm happy to see someone interresting in improving Alpha support, which
> > > > is .... very alpha for now !
> > >
> > > I'm interested in testing Alpha too, but I haven't seem a
> > > qemu-system-alpha show up yet. Alas, I have no hardware or specific
> > > expertise in this platform, I'm just trying to build and boot Linux
> > > kernels (and corresponding root filesystems) on as many emulated target
> > > platforms as I can.
> >
> > There are a lot of things missing for qemu-system-alpha to be available:
> > - the PALCode emulation is far from being complete or even usable
>
> I have no idea what that is.
The PALCode is mainly equivalent to the microcode of most CPU
architectures. What is different to microcode is that is uses only
regular Alpha instructions, just adding 4 instructions to access special
"hardware registers" and access the memory with different priviledge
levels. Another main idea is that everyone can write its own PALCode
image and switch to it at run-time. Then, for example, the PALCode ABI
is not the same one if you run Linux or Windows NT. The PALCode handles
all complex operations. For example, the CPU provides only TLB and the
MMU tables search is actually implemented in software, in the PALCode.
This greatly simplifies the CPU design and allows a high level of
flexibility. And if your OS need a specific ABI for example to handle
CPU exception, you define your ABI, write the PALCode using Alpha insns
and use it ! The Alpha CPU also provide an instruction to do PALCode
calls from the OS or applications.
There are 3 (4 ?) "native" PALCode ABIs documented in the Alpha CPUs
specifications then those can be emulated at the host side in Qemu. It
is in fact needed to emulate a subset of the PALCode even to run
user-mode programs.
[...]
--
J. Mayer <l_indien@magic.fr>
Never organized
next prev parent reply other threads:[~2007-10-21 11:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 9:19 [Qemu-devel] qemu alpha? Oliver Falk
2007-10-14 10:14 ` J. Mayer
2007-10-20 0:49 ` Rob Landley
2007-10-20 8:56 ` J. Mayer
2007-10-20 12:49 ` Thiemo Seufer
2007-10-21 9:00 ` J. Mayer
2007-10-20 13:39 ` Daniel Jacobowitz
2007-10-21 10:43 ` Rob Landley
2007-10-21 10:55 ` Paul Brook
2007-10-22 7:39 ` Oliver Falk
2007-10-21 11:06 ` J. Mayer [this message]
2007-10-22 7:43 ` Oliver Falk
2007-10-22 22:38 ` J. Mayer
2007-10-23 13:01 ` Brian Wheeler
2007-10-22 7:38 ` Oliver Falk
2007-10-20 8:59 ` Sunil Amitkumar Janki
2007-10-25 23:21 ` Rob Landley
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=1192964804.16781.75.camel@rapid \
--to=l_indien@magic.fr \
--cc=oliver@linux-kernel.at \
--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).