qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Patch] Ali Chipset support for PC [+ questions about alpha-softmmu target]
Date: Tue, 9 Sep 2008 19:16:48 +0300	[thread overview]
Message-ID: <f43fc5580809090916l643151c9jf3a4096e69c6556b@mail.gmail.com> (raw)
In-Reply-To: <1220975614.29130.86.camel@nibbler.dlib.indiana.edu>

On 9/9/08, Brian Wheeler <bdwheele@indiana.edu> wrote:
> Hello!
>
>  Long time listener, first time caller...
>
>  Since the ES40 Alpha Emulation project seems to have stalled, I've been
>  looking at what it would take to get QEmu to a state where it could
>  emulate an alpha machine.
>
>  The es40 is basically a PC with an alpha chip instead of an x86 and it
>  uses the Ali1543C south bridge.   This basically is a copy of piix_pci.c
>  so the chipset reports the ALI vendor and device codes to qemu when the
>  "alipc" machine type is selected.

IMHO pc.c would support more machines more cleanly if hardware
definition structures like Sparc ones were used.  Otherwise the patch
looks fine to me.

>  I've booted Knoppix and it seems to work ok...which is no surpise
>  considering how minor the changes are.
>
>  So, now to the questions:
>  * Is anyone else working on a softmmu target for the alpha?
>
>  * What state is the alpha cpu emulation in, and what's the best way to
>  test it?
>
>  * What's the most simple -softmmu target that could be used as a
>  starting point?

Depends on what you know, x86 is quite baroque but everyone knows the
basic architecture. Sparc32 is pretty simple.

>  * Where is the virtual->physical address translation code?  I peeked
>  around and couldn't find it very easily.

cpu_*_handle_mmu_fault(), usually in target-*/helper.c.

>  * Looking over some of the softmmu targets, it looks like the bulk of
>  target work (after the cpu emulation, of course) is just attaching all
>  of the devices in the right places.

True. Also it's not hard to create new devices.

  reply	other threads:[~2008-09-09 16:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-09 15:53 [Qemu-devel] [Patch] Ali Chipset support for PC [+ questions about alpha-softmmu target] Brian Wheeler
2008-09-09 16:16 ` Blue Swirl [this message]
2008-09-10  7:30 ` Tristan Gingold
2008-09-10 13:11   ` Brian Wheeler
2008-09-10 14:17     ` Tristan Gingold
2008-09-10 14:46       ` Paul Brook
2008-09-10 15:19         ` Tristan Gingold
2008-09-10 16:43           ` Paul Brook
2008-09-11 14:08           ` Laurent Desnogues
2008-09-11 14:17             ` Brian Wheeler
2008-09-10 15:42         ` Avi Kivity
2008-09-10 14:51       ` Brian Wheeler
2008-09-10 19:44 ` Hervé Poussineau

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=f43fc5580809090916l643151c9jf3a4096e69c6556b@mail.gmail.com \
    --to=blauwirbel@gmail.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).