From: Dirk Behme <dirk.behme@googlemail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Pending MIPS patches
Date: Mon, 26 Jun 2006 17:35:14 +0200 [thread overview]
Message-ID: <449FFEB2.1070305@gmail.com> (raw)
In-Reply-To: <449EBC39.3050701@bellard.org>
Fabrice Bellard wrote:
>> 2. [PATCH][MIPS] add "lwu" instruction
>> http://lists.gnu.org/archive/html/qemu-devel/2006-04/msg00326.html
>
>
> On which MIPS CPU is it defined ? Need to track instruction sets exactly
> to be able to select a given MIPS CPU at compile time or dynamically.
>
>> 3. [PATCH] Add special MIPS multiply instructions
>> http://lists.gnu.org/archive/html/qemu-devel/2006-04/msg00375.html
>
>
> Same remark.
These are NEC VR54xx specific extensions to the MIPS
instruction set.
They are used if you use GCC's -march=vr5400 option. See
www.necelam.com/docs/files/1375_V2.pdf
as well.
>> 9. [PATCH] Update MIPS status register with EXL and ERL bits at exception
>> http://lists.gnu.org/archive/html/qemu-devel/2006-06/msg00329.html
>
>
> OK but the following lines are suspicious:
Yes, I see. I mixed two fixes, let me explain below:
> - env->hflags = MIPS_HFLAG_ERL;
> + env->hflags |= MIPS_HFLAG_ERL;
This is a typo fix for a missing "or" (it should be "|="
instead of only "="). hflags is used as a shadow of the
status register and there not the whole value should be set,
only the corresponding flag. See for example correct usage
of MIPS_HFLAG_EXL or MIPS_HFLAG_ERL in helper.c or op.c of
target-mips. There, they are correctly used everywhere with
"|=" or "&= ~", except at this place.
> + env->CP0_Status &= (1 << CP0St_ERL);
This is part of the "Update status register EXL and ERL
flags directly, entering or leaving exception, not only hflags".
So this two added lines fix the missing "or" and set the
flag in the status register as well, not only in hflags.
If you like you can apply the single "|=" line as a typo
fix, and the rest as an additional fix to update status
register as well with ERL and EXL.
Regards
Dirk
Btw: Many thanks for commenting all patches!
next prev parent reply other threads:[~2006-06-26 15:35 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 [this message]
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
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=449FFEB2.1070305@gmail.com \
--to=dirk.behme@googlemail.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).