From: Piotras <piotras@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] page fault during ins
Date: Wed, 15 Dec 2004 09:22:50 +0100 [thread overview]
Message-ID: <da63183704121500221f3d21b9@mail.gmail.com> (raw)
In-Reply-To: <41BF5DBF.2050101@bellard.org>
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
Hi!
Maybe someone who experiences the problem could check the attached
patch? The patch is not really correct, but chances are it could help.
Regards,
Piotrek
On Tue, 14 Dec 2004 22:40:15 +0100, Fabrice Bellard <fabrice@bellard.org> wrote:
> Very interesting remark. If it explains a bug in one OS (for example the
> win 2000 disk full issue !), then it will become high priority.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: wnt.patch --]
[-- Type: text/x-patch; name="wnt.patch", Size: 675 bytes --]
diff -ru qemu-0.6.1/target-i386/translate.c qemu-0.6.1-A-prepare/target-i386/translate.c
--- qemu-0.6.1/target-i386/translate.c 2004-11-14 21:51:33.000000000 +0100
+++ qemu-0.6.1-A-prepare/target-i386/translate.c 2004-12-14 17:32:29.000000000 +0100
@@ -874,8 +874,10 @@
static inline void gen_ins(DisasContext *s, int ot)
{
- gen_op_in_DX_T0[ot]();
gen_string_movl_A0_EDI(s);
+ /* XXX: this is not correct, find another solution to avoid side-effect on restart (mmu fault) */
+ gen_op_st_T0_A0[ot + s->mem_index]();
+ gen_op_in_DX_T0[ot]();
gen_op_st_T0_A0[ot + s->mem_index]();
gen_op_movl_T0_Dshift[ot]();
if (s->aflag) {
next prev parent reply other threads:[~2004-12-15 8:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 14:52 [Qemu-devel] page fault during ins Piotras
2004-12-14 21:40 ` Fabrice Bellard
2004-12-14 22:29 ` malc
2004-12-15 8:17 ` Piotras
2004-12-17 0:07 ` Mark Williamson
2004-12-23 8:45 ` Benjamin Herrenschmidt
2004-12-15 8:22 ` Piotras [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-15 18:36 Juergen Keil
2004-12-15 20:07 ` Piotras
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=da63183704121500221f3d21b9@mail.gmail.com \
--to=piotras@gmail.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).