From: Gleb Natapov <gleb@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu, avi@redhat.com, mtosatti@redhat.com, zamsden@redhat.com
Subject: use of setjmp/longjmp in x86 emulator.
Date: Mon, 1 Mar 2010 11:18:19 +0200 [thread overview]
Message-ID: <20100301091819.GD16909@redhat.com> (raw)
I am looking at improving KVM x86 emulator. Current code does not
handle some special cases correctly (code execution from ROM, ins/outs
to/from MMIO) and many exception conditions during instruction emulation
are not handled correctly. There is a lot of code in emulator that is
there only for exception propagation. Using setjmp/longjmp will be very
beneficial here as exception condition during instruction execution
maps very naturally to setjmp/longjmp, so my question is what about
adding setjmp/longjmp implementation to the kernel, or alternatively,
if there is a fear that it can be abused, add it locally to emulator.c?
Note that instruction emulation is always done in process context.
--
Gleb.
next reply other threads:[~2010-03-01 9:18 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 9:18 Gleb Natapov [this message]
2010-03-01 12:45 ` use of setjmp/longjmp in x86 emulator Takuya Yoshikawa
2010-03-01 12:52 ` Gleb Natapov
2010-03-01 13:17 ` Takuya Yoshikawa
2010-03-01 13:26 ` Gleb Natapov
2010-03-01 19:13 ` john cooper
2010-03-02 7:28 ` Gleb Natapov
2010-03-07 9:00 ` Avi Kivity
2010-03-08 23:11 ` Eric W. Biederman
2010-03-09 6:28 ` Gleb Natapov
2010-03-01 16:13 ` Zachary Amsden
2010-03-01 17:47 ` Gleb Natapov
2010-03-01 18:39 ` Zachary Amsden
2010-03-01 18:47 ` Luca Barbieri
2010-03-01 19:03 ` Gleb Natapov
2010-03-01 19:18 ` Zachary Amsden
2010-03-01 22:31 ` H. Peter Anvin
2010-03-01 22:56 ` H. Peter Anvin
2010-03-01 23:34 ` Zachary Amsden
2010-03-01 23:43 ` H. Peter Anvin
2010-03-02 8:05 ` Gleb Natapov
2010-03-02 8:49 ` Gleb Natapov
2010-03-07 9:04 ` Avi Kivity
2010-03-08 0:08 ` H. Peter Anvin
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=20100301091819.GD16909@redhat.com \
--to=gleb@redhat.com \
--cc=avi@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mtosatti@redhat.com \
--cc=zamsden@redhat.com \
/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).