From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@redhat.com>
Subject: Re: [RFC PATCH 0/3] Real mode interrupt injection
Date: Tue, 10 Aug 2010 19:02:03 -0400
Message-ID: <4C61DA6B.60904@redhat.com>
References: <1281295456-11114-1-git-send-email-m.gamal005@gmail.com>	<4C60BF08.2050704@redhat.com> <AANLkTi=nq+7hPw1XLksP+ocVoKHxBS9vUEiKmw-GF-8Q@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: mtosatti@redhat.com, kvm@vger.kernel.org
To: Mohammed Gamal <m.gamal005@gmail.com>
Return-path: <kvm-owner@vger.kernel.org>
Received: from mx1.redhat.com ([209.132.183.28]:58819 "EHLO mx1.redhat.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S933782Ab0HJXCO (ORCPT <rfc822;kvm@vger.kernel.org>);
	Tue, 10 Aug 2010 19:02:14 -0400
In-Reply-To: <AANLkTi=nq+7hPw1XLksP+ocVoKHxBS9vUEiKmw-GF-8Q@mail.gmail.com>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

  On 08/10/2010 01:06 PM, Mohammed Gamal wrote:
> On 8/10/10, Avi Kivity<avi@redhat.com>  wrote:
>>    On 08/08/2010 03:24 PM, Mohammed Gamal wrote:
>>> This patch introduces real mode interrupt injection for VMX.
>>> It currently invokes the x86 emulator to emulate interrupts
>>> instead of manually setting VMX controls.
>>>
>>> Needless to say, this is not meant for merging in its current state.
>>> The emulator still needs some more work to get this completely
>>> operational.
>> Well, what happens when you run with it?
> The guest fails at two instances. First it sometimes encounters a
> group 7 instruction (0x0f 0x00), which the emulator doesn't emulate.
> Here is the relevant part of the trace:
>
> qemu-system-x86-4321  [001]   150.002191: kvm_entry: vcpu 0
>   qemu-system-x86-4321  [001]   150.002196: kvm_exit: reason
> IO_INSTRUCTION rip 0x3
>   qemu-system-x86-4321  [001]   150.002197: kvm_pio: pio_read at 0x70
> size 1 count 1
>   qemu-system-x86-4321  [001]   150.002205: kvm_entry: vcpu 0
>   qemu-system-x86-4321  [001]   150.002210: kvm_exit: reason
> IO_INSTRUCTION rip 0x5
>   qemu-system-x86-4321  [001]   150.002213: kvm_emulate_insn: f0000:5:
> e4 71 (real)
>   qemu-system-x86-4321  [001]   150.002215: kvm_pio: pio_write at 0x71
> size 1 count 1
>   qemu-system-x86-4321  [001]   150.002223: kvm_entry: vcpu 0
>   qemu-system-x86-4321  [001]   150.002228: kvm_exit: reason
> EXCEPTION_NMI rip 0x18
>   qemu-system-x86-4321  [001]   150.002229: kvm_page_fault: address
> ffff error_code f
>   qemu-system-x86-4321  [001]   150.002270: kvm_entry: vcpu 0
>   qemu-system-x86-4321  [001]   150.002276: kvm_exit: reason
> EXCEPTION_NMI rip 0x1a
>   qemu-system-x86-4321  [001]   150.002277: kvm_page_fault: address
> d4dc error_code f
>   qemu-system-x86-4321  [001]   150.002284: kvm_entry: vcpu 0
>   qemu-system-x86-4321  [001]   150.002289: kvm_exit: reason
> EXCEPTION_NMI rip 0x1d
>   qemu-system-x86-4321  [001]   150.002292: kvm_emulate_insn: f0000:1d:
> 0f 00 (real)

Could be a real instruction - we don't emulate all of group 7, and 
they're useful.

Can you put your bios.bin somewhere?  We can see what's there.

I'll look at the second case later.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.