From: Avi Kivity <avi@qumranet.com>
To: Mohammed Gamal <m.gamal005@gmail.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
kvm@vger.kernel.org, Rik van Riel <riel@surriel.com>,
Guillaume Thouvenin <guillaume.thouvenin@ext.bull.net>
Subject: Re: Questions on the VMentry failure patch
Date: Sat, 19 Jul 2008 10:41:05 +0300 [thread overview]
Message-ID: <48819A91.7040105@qumranet.com> (raw)
In-Reply-To: <52d4a3890807180904r7ba0e133l5f0362034ed434d9@mail.gmail.com>
Mohammed Gamal wrote:
>> It might be a host interrupt, forcing an exit (and an entry) at a random
>> point, which then fails.
>>
>> It might be a host interrupt, forcing an exit (and an entry) at a random
>> point, which then fails.
>>
>>
> I tried to disable vmexits on external interrupts in enter_rmode().
> And I get system lockups randomly as well. So I guess you're right
> about this too.
>
Disabling vmexits on external interrupts will certainly lock up your
host. As soon as the guest pages in enough memory to run a loop waiting
for an interrupt, nothing will cause it to come out.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
prev parent reply other threads:[~2008-07-19 7:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 14:07 Questions on the VMentry failure patch Mohammed Gamal
2008-07-07 14:24 ` Avi Kivity
2008-07-07 14:44 ` Mohammed Gamal
2008-07-07 14:52 ` Avi Kivity
2008-07-07 15:26 ` Anthony Liguori
2008-07-07 15:29 ` Anthony Liguori
2008-07-08 0:52 ` Mohammed Gamal
2008-07-09 17:56 ` Mohammed Gamal
2008-07-10 13:48 ` Mohammed Gamal
2008-07-14 16:10 ` Mohammed Gamal
2008-07-14 16:12 ` Avi Kivity
2008-07-14 16:15 ` Anthony Liguori
2008-07-14 16:24 ` Avi Kivity
2008-07-14 17:09 ` Mohammed Gamal
2008-07-18 16:04 ` Mohammed Gamal
2008-07-19 7:41 ` 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=48819A91.7040105@qumranet.com \
--to=avi@qumranet.com \
--cc=anthony@codemonkey.ws \
--cc=guillaume.thouvenin@ext.bull.net \
--cc=kvm@vger.kernel.org \
--cc=m.gamal005@gmail.com \
--cc=riel@surriel.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.