From: Avi Kivity <avi@redhat.com>
To: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
Cc: mtosatti@redhat.com, gleb@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH v3 0/4] KVM: rework of "Fix x86 emulator's fault propagations"
Date: Wed, 17 Feb 2010 15:32:17 +0200 [thread overview]
Message-ID: <4B7BEFE1.1090207@redhat.com> (raw)
In-Reply-To: <20100212155044.96fb69f6.yoshikawa.takuya@oss.ntt.co.jp>
On 02/12/2010 08:50 AM, Takuya Yoshikawa wrote:
> This is the rework of "Fix x86 emulator's fault propagations".
> -- http://www.spinics.net/lists/kvm/msg28874.html
>
> I read the review comments from Avi, Marcelo and Gleb and removed
> some parts which should be done with more care: descriptor related
> part and emulator_sys* part.
>
> Now the contents is like this:
> - patch 1: X86EMUL macro replacements: from do_fetch_insn_byte()
> to x86_decode_insn()
> - patch 2: X86EMUL macro replacements: x86_emulate_insn() and its
> helpers
> - patch 3: Fix x86_emulate_insn() not to use the variable rc for
> non-X86EMUL values
> - patch 4: Tiny fix: remove redundant prototype of load_pdptrs()
>
>
>
Applied all, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2010-02-17 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-12 6:50 [PATCH v3 0/4] KVM: rework of "Fix x86 emulator's fault propagations" Takuya Yoshikawa
2010-02-12 6:53 ` [PATCH v3 1/4] KVM: X86EMUL macro replacements: from do_fetch_insn_byte() to x86_decode_insn() Takuya Yoshikawa
2010-02-12 6:57 ` [PATCH v3 2/4] KVM: X86EMUL macro replacements: x86_emulate_insn() and its helpers Takuya Yoshikawa
2010-02-12 7:00 ` [PATCH v3 3/4] KVM: Fix x86_emulate_insn() not to use the variable rc for non-X86EMUL values Takuya Yoshikawa
2010-02-12 7:02 ` [PATCH v3 4/4] KVM: Tiny fix: remove redundant prototype of load_pdptrs() Takuya Yoshikawa
2010-02-12 7:09 ` [PATCH v3 0/4] KVM: rework of "Fix x86 emulator's fault propagations" Gleb Natapov
2010-02-17 13:32 ` Avi Kivity [this message]
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=4B7BEFE1.1090207@redhat.com \
--to=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=yoshikawa.takuya@oss.ntt.co.jp \
/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