From: Avi Kivity <avi@redhat.com>
To: Mohammed Gamal <m.gamal005@gmail.com>
Cc: mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: [RFC PATCH 0/3] Real mode interrupt injection
Date: Sun, 15 Aug 2010 15:23:27 +0300 [thread overview]
Message-ID: <4C67DC3F.9080509@redhat.com> (raw)
In-Reply-To: <AANLkTinVVs1bvGQAa32OTjNnZ8i1XB3YeSFRDaeJVP1u@mail.gmail.com>
On 08/12/2010 04:07 AM, Mohammed Gamal wrote:
>>>
>>> I was playing around with the non-atomic-injection branch. I decided
>>> to use e_i_g_s=1, and it's worth noting that I never experienced these
>>> faults with the switch enabled.
> Hate to spoil it. I did experience the faults again with e_i_g_s=1,
> although much less frequently.
>
> What is rather really strange, is that I could get a Linux guest to
> boot up completely both with e_i_g_s=1 and without it with the real
> mode interrupt patch enabled. It looks to me like the problem mainly
> happens when the BIOS tranfers control to the boot loader. Other
> guests usually fail.
>
> Would you like me to attach a trace?
It will be much too big, upload it somewhere or send it to be privately.
But, use the code with the interrupt injection setup fixed (see my
comment to patch 2).
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-08-15 15:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-08 19:24 [RFC PATCH 0/3] Real mode interrupt injection Mohammed Gamal
2010-08-08 19:24 ` [RFC PATCH 1/3] x86 emulator: Expose emulate_int_real() Mohammed Gamal
2010-08-08 19:24 ` [RFC PATCH 2/3] x86: Add inject_realmode_interrupt() wrapper Mohammed Gamal
2010-08-10 2:57 ` Avi Kivity
2010-08-08 19:24 ` [RFC PATCH 3/3] VMX: Emulated real mode interrupt injection Mohammed Gamal
2010-08-10 3:03 ` Avi Kivity
2010-08-10 17:13 ` Mohammed Gamal
2010-08-10 22:52 ` Avi Kivity
2010-08-10 2:52 ` [RFC PATCH 0/3] Real " Avi Kivity
2010-08-10 17:06 ` Mohammed Gamal
2010-08-10 23:02 ` Avi Kivity
2010-08-11 1:19 ` Mohammed Gamal
[not found] ` <AANLkTimmhvH2q7cCJZ+AV0OYhbvz=AZ_LLA3jU-nLdF1@mail.gmail.com>
2010-08-11 11:04 ` Avi Kivity
2010-08-11 11:20 ` Avi Kivity
2010-08-11 12:08 ` Avi Kivity
2010-08-11 23:22 ` Mohammed Gamal
2010-08-12 0:48 ` Avi Kivity
2010-08-12 1:07 ` Mohammed Gamal
2010-08-15 12:23 ` Avi Kivity [this message]
2010-08-15 12:30 ` Mohammed Gamal
2010-08-11 11:15 ` 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=4C67DC3F.9080509@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 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.