From: Stefan Weil <weil@mail.berlios.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu/target-mips op.c translate.c
Date: Fri, 18 May 2007 20:08:28 +0200 [thread overview]
Message-ID: <464DEB9C.60701@mail.berlios.de> (raw)
In-Reply-To: <E1Hor1p-0002Zr-U1@cvs>
This change still does not fix the problems with
self-modifying code in Linux FPU emulation.
Linux FPU emulation calls mips_dsemul which calls flush_cache_sigtramp
which is local_r4k_flush_cache_sigtramp for MIPS 4KEc. So I had expected
that the new code would fix the problems with FPU emulation.
But programs like aptitude crash (caused by FPU emulation)
even with latest QEMU CVS.
Stefan
Thiemo Seufer schrieb:
> CVSROOT: /sources/qemu
> Module name: qemu
> Changes by: Thiemo Seufer <ths> 07/05/18 01:13:09
>
> Modified files:
> target-mips : op.c translate.c
>
> Log message:
> Work around the lack of proper handling for self-modifying code.
>
> CVSWeb URLs:
> http://cvs.savannah.gnu.org/viewcvs/qemu/target-mips/op.c?cvsroot=qemu&r1=1.55&r2=1.56
> http://cvs.savannah.gnu.org/viewcvs/qemu/target-mips/translate.c?cvsroot=qemu&r1=1.78&r2=1.79
next prev parent reply other threads:[~2007-05-18 18:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 1:13 [Qemu-devel] qemu/target-mips op.c translate.c Thiemo Seufer
2007-05-18 18:08 ` Stefan Weil [this message]
2007-05-18 19:50 ` Thiemo Seufer
2007-05-18 20:27 ` Paul Brook
2007-05-19 10:47 ` Stefan Weil
-- strict thread matches above, loose matches on Subject: below --
2007-05-23 8:18 Thiemo Seufer
2007-05-19 17:45 Thiemo Seufer
2007-05-13 18:39 Thiemo Seufer
2007-05-11 17:08 Thiemo Seufer
2007-05-11 9:59 Thiemo Seufer
2007-05-09 9:33 Thiemo Seufer
2007-04-15 21:26 Thiemo Seufer
2007-04-14 12:56 Thiemo Seufer
2007-04-11 2:13 Thiemo Seufer
2007-04-09 14:17 Thiemo Seufer
2007-04-09 14:15 Thiemo Seufer
2007-04-09 14:13 Thiemo Seufer
2007-04-05 23:16 Thiemo Seufer
2007-02-27 19:27 Thiemo Seufer
2006-12-07 20:07 Thiemo Seufer
2006-11-12 23:54 Paul Brook
2006-10-23 21:25 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=464DEB9C.60701@mail.berlios.de \
--to=weil@mail.berlios.de \
--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).