From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Pending MIPS patches
Date: Sun, 25 Jun 2006 18:39:21 +0200 [thread overview]
Message-ID: <449EBC39.3050701@bellard.org> (raw)
In-Reply-To: <449EB5FA.6070405@gmail.com>
Dirk Behme wrote:
> Hi,
>
> just fyi below my list of pending MIPS patches. Not sure if all patches
> are ready for inclusion, but maybe they are helpful for somebody. I try
> to track which patches are already applied and which not. Please feel
> free to add, comment, discuss etc anything.
>
> Best regards
>
> Dirk
>
> Pending MIPS patches (bugs & improvements):
> ===========================================
>
> 1. [PATCH] Huge TLB performance improvement
> http://lists.gnu.org/archive/html/qemu-devel/2006-03/msg00034.html
Need to verify that it does not slow down x86 target.
> 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.
> 4. [PATCH][MIPS] Enforce aligned pc
> http://lists.gnu.org/archive/html/qemu-devel/2006-04/msg00484.html
Can it happen on a real MIPS ? If not, an assert should be used for example.
> 5.[PATCH 5-6/8] Mips improvements
OK. Maybe expanding only the performance critical CP0 insn would have
sufficed ?
> http://lists.gnu.org/archive/html/qemu-devel/2006-05/msg00314.html
> http://lists.gnu.org/archive/html/qemu-devel/2006-05/msg00315.html
>
> Note: Patch 7/8 was eaten by list.
>
> 6. [PATCH] Fix initial value for MIPS CP0 Config Register
> http://lists.gnu.org/archive/html/qemu-devel/2006-05/msg00372.html
Already done.
> 7. [PATCH] Restructure MIPS r4k code
> http://lists.gnu.org/archive/html/qemu-devel/2006-05/msg00429.html
> Note: Pending until additional MIPS machines are added. Comment from
> Fabrice: I prefer to wait until there is another mips machine (e.g. Malta).
> Currently I see no reason to move the mips code as it is very small.
>
> 8. [PATCH] Add mips-user signal handling
> http://lists.gnu.org/archive/html/qemu-devel/2006-06/msg00319.html
OK. Need to check the handling of "env->PC += 4" in linux-user/main.c. I
want to be sure there is not a better solution. Adding setup_rt_frame
would be good too.
> 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:
} else {
env->CP0_ErrorEPC = env->PC;
}
- env->hflags = MIPS_HFLAG_ERL;
+ env->hflags |= MIPS_HFLAG_ERL;
+ env->CP0_Status &= (1 << CP0St_ERL);
pc = 0xBFC00000;
Fabrice.
next prev parent reply other threads:[~2006-06-25 16:41 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 [this message]
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
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=449EBC39.3050701@bellard.org \
--to=fabrice@bellard.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.