From: Avi Kivity <avi@qumranet.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Mohammed Gamal <m.gamal005@gmail.com>,
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: Mon, 14 Jul 2008 19:24:08 +0300 [thread overview]
Message-ID: <487B7DA8.9070500@qumranet.com> (raw)
In-Reply-To: <487B7B9A.7030907@codemonkey.ws>
Anthony Liguori wrote:
>>
>> I suspected an interrupt, which fits the scenario you describe.
>> Although Anthony tested this and found out interrupts were not
>> involved, IIRC.
>
> It was at least not occurring for me when an interrupt was being
> injected. That's not to say that it isn't somehow affected by
> interrupt injections but it doesn't appear to be the obvious interrupt
> occurs while doing switch_to_pm_20.
A good thing to check is whether guest interrupts are enabled at that
point. I suspect they aren't.
It might be a host interrupt, forcing an exit (and an entry) at a random
point, which then fails.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-07-14 16:24 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 [this message]
2008-07-14 17:09 ` Mohammed Gamal
2008-07-18 16:04 ` Mohammed Gamal
2008-07-19 7:41 ` 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=487B7DA8.9070500@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox