From: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
To: Gleb Natapov <gleb@redhat.com>
Cc: avi@redhat.com, mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH v2 0/8] Fix x86 emulator's fault propagations
Date: Fri, 12 Feb 2010 09:42:05 +0900 [thread overview]
Message-ID: <4B74A3DD.6050301@oss.ntt.co.jp> (raw)
In-Reply-To: <20100210152757.GH24949@redhat.com>
Gleb Natapov wrote:
> On Wed, Feb 10, 2010 at 10:45:41AM +0900, Takuya Yoshikawa wrote:
>> My motivation: What I want to achive by this
>> work is to make the basic style of x86 emulator
>> better for the following developments. Actually
>> unless we handle the fault properly, our works
>> implementing each instruction's emulation may
>> end up with no effect.
> Why do you want to emulate every instruction?
>
> --
> Gleb.
No, I do not think we have to emulate every instruction.
I might write something misleading.
But I want to know which instructions or modes are not implemented
yet but have to be implemented in the future, if they may effect
to end users. We may get some questions like "Are there any
instructions which are not supported by KVM?" in the future:
because (advanced)customers will find "FIXME" in the source code.
next prev parent reply other threads:[~2010-02-12 0:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 1:45 [PATCH v2 0/8] Fix x86 emulator's fault propagations Takuya Yoshikawa
2010-02-10 1:50 ` [PATCH v2 1/8] KVM: Fix load_guest_segment_descriptor() to inject page fault Takuya Yoshikawa
2010-02-10 16:25 ` Avi Kivity
2010-02-10 16:29 ` Marcelo Tosatti
2010-02-12 0:22 ` Takuya Yoshikawa
2010-02-10 16:43 ` Gleb Natapov
2010-02-12 0:19 ` Takuya Yoshikawa
2010-02-12 0:13 ` Takuya Yoshikawa
2010-02-10 1:53 ` [PATCH v2 2/8] Fix kvm_load_segment_descriptor()'s fault propagation Takuya Yoshikawa
2010-02-10 1:56 ` [PATCH v2 3/8] Fix x86_emulate_insn() to handle faults propagated from kvm_load_segment_descriptor() Takuya Yoshikawa
2010-02-10 2:01 ` [PATCH v2 4/8] X86EMUL macro replacements: from do_fetch_insn_byte() to x86_decode_insn() Takuya Yoshikawa
2010-02-10 2:04 ` [PATCH v2 5/8] X86EMUL macro replacements: x86_emulate_insn() and its helpers Takuya Yoshikawa
2010-02-10 2:07 ` [PATCH v2 6/8] Fix x86_emulate_insn() not to use rc variable for non-X86EMUL values Takuya Yoshikawa
2010-02-10 2:13 ` [PATCH v2 7/8] Fix emulate_sys[call, enter, exit]()'s fault handling Takuya Yoshikawa
2010-02-10 2:16 ` [PATCH v2 8/8] Tiny fix: remove redundant prototype of of load_pdptrs() Takuya Yoshikawa
2010-02-10 15:27 ` [PATCH v2 0/8] Fix x86 emulator's fault propagations Gleb Natapov
2010-02-12 0:42 ` Takuya Yoshikawa [this message]
2010-02-10 16:57 ` Avi Kivity
2010-02-10 16:58 ` Gleb Natapov
2010-02-12 0:44 ` Takuya Yoshikawa
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=4B74A3DD.6050301@oss.ntt.co.jp \
--to=yoshikawa.takuya@oss.ntt.co.jp \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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