From: Thiemo Seufer <ths@networkno.de>
To: Stefan Weil <weil@mail.berlios.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] MIPS instruction set configuration
Date: Mon, 3 Jul 2006 20:58:25 +0100 [thread overview]
Message-ID: <20060703195825.GA25654@networkno.de> (raw)
In-Reply-To: <44A964C1.307@mail.berlios.de>
Stefan Weil wrote:
> Hi all,
>
> just for information about current projects for QEMU MIPS:
>
> my machine is AR7 which includes a MIPS 4KEc core.
> This core supports the MIPS32R2 architecture and has no FPU.
>
> As far as I know the MIPS architecture, most CPU features
> can be read from well defined bits and bytes in the CP0 registers.
>
> These registers should be set by every machine definition in QEMU.
>
> So the emulation (translator) code could get all information needed from
> the CP0 registers which are part of variable "env". There is no
> need to introduce new defines or variables to get endianess,
> instruction set, presence of FPU or internal timer, and other
> features.
This is mostly true for MIPS32 (and later) conforming CPUs. Earlier ones
(like the vr5400 Dirk is interested in) didn't announce all their
capabilities via config registers, and coprocessor CP0, where the
config registers reside, wasn't standardised.
> And if generic property bits are not enough:
> the processor identification is part of the CP0 registers, too.
>
> Of course, one might mirror some features in extra variables for
> performance reasons.
>
> What do you think of my proposal?
It only works for the more modern CPUs. I think we have to invert the
scheme, that is, keep the "master copy" of the configuration in an
opaque place, and feed the config registers from there.
Thiemo
next prev parent reply other threads:[~2006-07-03 19:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-25 16:12 [Qemu-devel] Pending MIPS patches Dirk Behme
2006-06-25 16:39 ` Fabrice Bellard
2006-06-26 9:35 ` Marius Groeger
2006-06-26 15:35 ` Dirk Behme
2006-06-26 20:17 ` Fabrice Bellard
2006-06-27 15:45 ` MIPS instruction set configuration, was: " Dirk Behme
2006-06-27 15:55 ` [Qemu-devel] Re: MIPS instruction set configuration Marius Groeger
2006-06-27 20:57 ` Fabrice Bellard
2006-07-02 16:27 ` [Qemu-devel] [PATCH] " Dirk Behme
2006-07-02 23:16 ` Thiemo Seufer
2006-07-03 8:32 ` Fabrice Bellard
2006-07-03 9:50 ` Thiemo Seufer
2006-07-03 14:32 ` Dirk Behme
2006-07-03 14:53 ` Fabrice Bellard
2006-07-08 6:15 ` Dirk Behme
2006-07-03 14:20 ` Dirk Behme
2006-07-03 17:02 ` Thiemo Seufer
2006-07-03 18:41 ` Stefan Weil
2006-07-03 19:58 ` Thiemo Seufer [this message]
2006-07-08 6:19 ` Dirk Behme
2006-07-08 12:47 ` Thiemo Seufer
[not found] ` <44A001C7.8040303@gmail.com>
2006-06-26 17:27 ` [Qemu-devel] Pending MIPS patches Raphaël Rigo
2006-06-27 21:08 ` Fabrice Bellard
2006-06-27 21:15 ` Fabrice Bellard
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=20060703195825.GA25654@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).