From: "Nickolai Zeldovich" <nickolai@cs.stanford.edu>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] fix exception precision for cmpxchg8b
Date: Tue, 24 Apr 2007 19:47:14 -0700 [thread overview]
Message-ID: <12b5f1ef0704241947q50309a5fyda7f4c6bfba59667@mail.gmail.com> (raw)
In qemu-0.9.0, an exception in cmpxchg8b (e.g. page fault due to a
missing TLB entry) causes the wrong eip value to be pushed onto the
exception stack -- it seems to be the eip of the last exception or the
start of the translation block, whichever happened last. This makes
it impossible to resume execution after such an exception.
The simple patch below fixes it, by explicitly saving the current eip
before invoking the cmpxchg8b helper; the same approach appears to be
taken in many other instructions before generating code that could
raise an exception. Apologies for the non-tab-clean patch, but it's
simple enough to apply by hand.
I can't quite understand what's generating the equivalent piece of
code (to save pc_start into eip) for the cmpxchgl instruction (defined
right above cmpxchg8b in translate.c). I'd be thankful if someone
could explain to me where it's getting saved.
Nickolai.
--- qemu-0.9.0/target-i386/translate.c 2007-02-05 15:01:54.000000000 -0800
+++ /home/nickolai/build/qemu-0.9.0/target-i386/translate.c 2007-04-24
19:33:47.000000000 -0700
@@ -3800,6 +3800,7 @@
if (s->cc_op != CC_OP_DYNAMIC)
gen_op_set_cc_op(s->cc_op);
gen_lea_modrm(s, modrm, ®_addr, &offset_addr);
+ gen_jmp_im(pc_start - s->cs_base);
gen_op_cmpxchg8b();
s->cc_op = CC_OP_EFLAGS;
break;
next reply other threads:[~2007-04-25 2:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 2:47 Nickolai Zeldovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-04-25 3:59 [Qemu-devel] [PATCH] fix exception precision for cmpxchg8b Ben Taylor
2007-04-25 4:11 ` Nickolai Zeldovich
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=12b5f1ef0704241947q50309a5fyda7f4c6bfba59667@mail.gmail.com \
--to=nickolai@cs.stanford.edu \
--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).