public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Dong, Eddie" <eddie.dong@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: Fix kernel pio emulation mistake
Date: Sun, 22 Mar 2009 11:09:55 +0200	[thread overview]
Message-ID: <49C60063.10205@redhat.com> (raw)
In-Reply-To: <9832F13BD22FB94A829F798DA4A8280501A1D68ACD@pdsmsx503.ccr.corp.intel.com>

Dong, Eddie wrote:
>> kvm_emulate_pio() returns 1 when emulation is complete,
>> and 0 when emulation needs further processing in
>> userspace.  So I think in both cases cannot_emulate is
>> the wrong answer.  I think 'in' emulation gets it right.
>>     
>
> OK, yes. Do u mean this?  I may misunderstand.
>
> Thx, eddie
>
> diff --git a/arch/x86/kvm/x86_emulate.c b/arch/x86/kvm/x86_emulate.c
> index ca91749..838fdc9 100644
> --- a/arch/x86/kvm/x86_emulate.c
> +++ b/arch/x86/kvm/x86_emulate.c
> @@ -1838,11 +1838,11 @@ special_insn:
>  		io_dir_in = 0;
>  	do_io:	if (kvm_emulate_pio(ctxt->vcpu, NULL, io_dir_in,
>  				   (c->d & ByteOp) ? 1 : c->op_bytes,
> -				   port) != 0) {
> +				   port) == 0) {
>  			c->eip = saved_eip;
> -			goto cannot_emulate;
> +			return -1;
>  		}
> -		break;
> +		return 0;
>  	case 0xf4:              /* hlt */
>  		ctxt->vcpu->arch.halt_request = 1;
>  		break; 

I think this is right, but can you add a testcase to 
user/test/x86/realmode.c?

(you need to set the emulate_invalid_guest_state module parameter to 1 
to run this test)

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


      reply	other threads:[~2009-03-22  9:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19  7:06 Fix kernel pio emulation mistake Dong, Eddie
2009-03-19  9:35 ` Avi Kivity
2009-03-20  9:07   ` Dong, Eddie
2009-03-22  9:09     ` 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=49C60063.10205@redhat.com \
    --to=avi@redhat.com \
    --cc=eddie.dong@intel.com \
    --cc=kvm@vger.kernel.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