From: Fabrice Bellard <fabrice@bellard.org>
To: "Raphaël Rigo" <ml-qemu@twilight-hall.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Pending MIPS patches
Date: Tue, 27 Jun 2006 23:08:29 +0200 [thread overview]
Message-ID: <44A19E4D.2090005@bellard.org> (raw)
In-Reply-To: <44A018E4.50708@twilight-hall.net>
Raphaël Rigo wrote:
> Dirk Behme wrote:
>
>> Hi Raphaël,
>>
>> maybe you find some time and like to answer to Fabrice's remark
>> regarding patch 8
>> below?
>>
>> http://lists.gnu.org/archive/html/qemu-devel/2006-06/msg00419.html
>>
>> Would be nice to get as many of the pending MIPS patches applied as
>> possible.
>>
>> Many thanks
>>
>> Dirk
>>
>> Fabrice Bellard wrote:
>>
>>>> Pending MIPS patches (bugs & improvements):
>>>> ===========================================
>>
>>
>>>> 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.
>
> Hello,
> there are 2 possibilities to handle this env->PC += 4:
> - do a special case wrapper here to avoid increasing PC when it's
> a sigreturn.
> - in do_sigreturn set PC with a -4 offset.
> I chose the first way because I thought it would be cleaner, if anyone
> was to change this part of the code, then it would be clear that
> sigreturn directly sets PC. Using the 2nd possibility, one could change
> this += 4 without knowing do_sigreturn would be affected.
>
> I also checked if we could get rid of this weird piece of code, but
> could not find a clear way to do so.
>
> So i preferred maintainability over efficiency, but if you think
> setting PC with an offset of -4 in signal.c is better, tell me and i
> will update the patch.
There is another simpler solution and I applied it. BTW, the Linux
kernel uses the same solution :-)
Fabrice.
next prev parent reply other threads:[~2006-06-27 21:48 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
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 [this message]
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=44A19E4D.2090005@bellard.org \
--to=fabrice@bellard.org \
--cc=ml-qemu@twilight-hall.net \
--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).