qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Choose emulated MIPS CPU at runtime
Date: Tue, 6 Mar 2007 21:05:01 +0000	[thread overview]
Message-ID: <20070306210501.GC16210@networkno.de> (raw)
In-Reply-To: <45EDBEA0.8070401@mail.berlios.de>

Stefan Weil wrote:
> Thiemo Seufer schrieb:
> > Looks very nice, except that the CPU models are out of touch with
> > reality. :-)
> > - There is no CPU called "R4Kc" etc.
> > - What Qemu emulates is currently close to a 4KEc with an R3000-style
> > FPU attached. (A 4KEc is a 4Kc with MIPS32R2 instructions.)
> There exists also an older 4KEc version which only supports
> MIPS32R1. AR7 (a SoC from TI) is based on this older version.

This can't be correct. 4KEc is defined as a MIPS32R2 core by MIPS
Technologies. A MIPS32R1 4KEc would be redundant since that's what
the 4Kc is.

> I noticed this because some code using DI worked well with QEMU,
> but my AR7 based DSL router crashed...

Did it die with an RI exception? If not then it sounds more like
a missing ehb barrier. Qemu doesn't emulate pipeline hazards...

> AR7, it would be nice to switch between MIPS32R1 / MIPS32R2
> instruction sets.

It would be nice to see a AR7 router emulation as a separate
machine type in Qemu. *hint* *hint* :-)

> I think this could be done similar to the FPU
> switch, but I don't have a list of the differences, and there are
> no MIPS32R2 markers in the QEMU code :-(

The specificiation for MIPS{32,64}R{1,2} used to be hidden behind a
"free registration" nag screen at http://www.mips.com/ . Unfortunately
it isn't ATM, it apparently fell through the cracks of the website
relaunch.


Thiemo

  reply	other threads:[~2007-03-06 21:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-06 15:47 [Qemu-devel] [PATCH] Choose emulated MIPS CPU at runtime Hervé Poussineau
2007-03-06 17:09 ` Daniel Jacobowitz
2007-03-06 17:37 ` Thiemo Seufer
2007-03-06 19:18   ` Stefan Weil
2007-03-06 21:05     ` Thiemo Seufer [this message]
2007-03-06 21:13       ` Thiemo Seufer
2007-03-06 22:44       ` Stefan Weil
2007-03-25 16:46         ` Thiemo Seufer

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=20070306210501.GC16210@networkno.de \
    --to=ths@networkno.de \
    --cc=qemu-devel@nongnu.org \
    --cc=weil@mail.berlios.de \
    /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).