From: Avi Kivity <avi@redhat.com>
To: Mohammed Gamal <m.gamal005@gmail.com>
Cc: kvm@vger.kernel.org, mtosatti@redhat.com
Subject: Re: [RFC PATCH v3 0/4] Real mode interrupt injection
Date: Mon, 16 Aug 2010 16:19:06 +0300 [thread overview]
Message-ID: <4C693ACA.9090702@redhat.com> (raw)
In-Reply-To: <AANLkTik5ZQ5cRu6JmHN8HAN3mu-m9EgKh=UHRPndzmUq@mail.gmail.com>
On 08/16/2010 02:37 AM, Mohammed Gamal wrote:
> On Mon, Aug 16, 2010 at 12:46 AM, Mohammed Gamal<m.gamal005@gmail.com> 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.
>>
>> Mohammed Gamal (4):
>> x86 emulator: Expose emulate_int_real()
>> x86: Separate emulation context initialization in a separate function
>> x86: Add kvm_inject_realmode_interrupt() wrapper
>> VMX: Emulated real mode interrupt injection
>>
>> arch/x86/include/asm/kvm_emulate.h | 3 +-
>> arch/x86/kvm/vmx.c | 65 +++----------------------------
>> arch/x86/kvm/x86.c | 75 ++++++++++++++++++++++--------------
>> arch/x86/kvm/x86.h | 1 +
>> 4 files changed, 55 insertions(+), 89 deletions(-)
>> ---
>> Changes since v2:
>> - Refactored emulation context initialization code
>> - Commit eip value from the decode cache to the emulation context in x86.c rather than the emulator
>> - Add kvm_* prefix to inject_realmode_interrupt() global symbol for consistency
>>
> Here is a full trace of a MINIX guest since bootup. Looks like we get
> stuck somewhere in the BIOS.
> https://docs.google.com/leaf?id=0B9UodZT1IuENMzJhNWQxM2YtYzE3YS00YWY4LTk2YTgtZWY3ODNhMWUxMDkx&sort=name&layout=list&num=50
I debugged this for a bit - emulate_int_real() is completely broken.
emulate_push() doesn't push anything, it only schedules a push; running
these back-to-back will result in only the last push to be executed.
With that fixed, I get the boot splash. Not 100% perfect but much closer.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-08-16 13:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-15 21:46 [RFC PATCH v3 0/4] Real mode interrupt injection Mohammed Gamal
2010-08-15 21:47 ` [RFC PATCH v3 1/4] x86 emulator: Expose emulate_int_real() Mohammed Gamal
2010-08-15 21:47 ` [RFC PATCH v3 2/4] x86: Separate emulation context initialization in a separate function Mohammed Gamal
2010-08-15 21:47 ` [RFC PATCH v3 3/4] x86: Add kvm_inject_realmode_interrupt() wrapper Mohammed Gamal
2010-08-15 21:47 ` [RFC PATCH v3 4/4] VMX: Emulated real mode interrupt injection Mohammed Gamal
2010-08-15 23:37 ` [RFC PATCH v3 0/4] Real " Mohammed Gamal
2010-08-16 8:51 ` Avi Kivity
2010-08-16 13:19 ` Avi Kivity [this message]
2010-08-16 13:28 ` Mohammed Gamal
2010-08-16 14:16 ` Avi Kivity
2010-08-16 14:29 ` Gleb Natapov
2010-08-16 14:47 ` Avi Kivity
2010-08-16 15:23 ` Mohammed Gamal
2010-08-16 15:31 ` Gleb Natapov
2010-08-16 15:33 ` Avi Kivity
2010-08-16 15:43 ` Mohammed Gamal
2010-08-16 10:14 ` Avi Kivity
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=4C693ACA.9090702@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=m.gamal005@gmail.com \
--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