All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH 1/4] KVM: Fix x86_decode_insn() return code check
Date: Thu, 13 Jan 2011 15:54:43 +0200	[thread overview]
Message-ID: <4D2F0423.4050708@redhat.com> (raw)
In-Reply-To: <1294146884-6253-2-git-send-email-avi@redhat.com>

On 01/04/2011 03:14 PM, Avi Kivity wrote:
> x86_decode_insn() doesn't return X86EMUL_* values, it returns
> EMULATION_* codes.  Adjust the check.
>
> Signed-off-by: Avi Kivity<avi@redhat.com>
> ---
>   arch/x86/kvm/x86.c |    2 +-
>   1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index fa708c9..b20499d 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -4391,7 +4391,7 @@ int x86_emulate_instruction(struct kvm_vcpu *vcpu,
>   		vcpu->arch.emulate_ctxt.perm_ok = false;
>
>   		r = x86_decode_insn(&vcpu->arch.emulate_ctxt, insn, insn_len);
> -		if (r == X86EMUL_PROPAGATE_FAULT)
> +		if (r != EMULATION_OK)
>   			goto done;
>
>   		trace_kvm_emulate_insn_start(vcpu);

Strangely, this patch causes a failure in Windows XP.  Dropping until 
submitter investigates and fixes.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2011-01-13 13:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04 13:14 [PATCH 0/4] Vendor specific instructions and the emulator Avi Kivity
2011-01-04 13:14 ` [PATCH 1/4] KVM: Fix x86_decode_insn() return code check Avi Kivity
2011-01-13 13:54   ` Avi Kivity [this message]
2011-01-04 13:14 ` [PATCH 2/4] KVM: Simplify exit path on decode failure Avi Kivity
2011-01-10 17:17   ` Jan Kiszka
2011-01-11  9:40     ` Avi Kivity
2011-01-04 13:14 ` [PATCH 3/4] KVM: x86 emulator: vendor specific instructions Avi Kivity
2011-01-04 13:14 ` [PATCH 4/4] KVM: Drop ad-hoc vendor specific instruction restriction Avi Kivity
2011-01-07  9:49 ` [PATCH 0/4] Vendor specific instructions and the emulator Marcelo Tosatti

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=4D2F0423.4050708@redhat.com \
    --to=avi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.