public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Mohammed Gamal <m.gamal005@gmail.com>
Cc: Jan Kiszka <jan.kiszka@web.de>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Anthony Liguori <anthony@codemonkey.ws>,
	kvm@vger.kernel.org, Rik van Riel <riel@surriel.com>
Subject: Re: [Regression] kvm-userspace: VM freezes after booting FreeDOS
Date: Sun, 13 Jul 2008 13:08:50 +0300	[thread overview]
Message-ID: <4879D432.6030104@qumranet.com> (raw)
In-Reply-To: <52d4a3890807130226t40ed349eq3b5e367754d64978@mail.gmail.com>

Mohammed Gamal wrote:
>
>>>> +        vmx_inject_irq(vcpu, vec);
>>>>
>>>>         
>>> kvm_queue_exception()
>>>       
>> OK.
>>     
>
> Not so fast, the GP# pops up again with kvm_queue_exception(). Why
> should we use kvm_queue_exception() here? 

kvm_queue_exception() will also block interrupt injection.  Without 
this, there's the risk that the breakpoint injection will be overridden 
by a following interrupt injection.

> Shouldn't this be the part
> where we handle/service that exception, rather than adding it, may be
> I am misunderstanding so CIIW.
>   

It is indeed where we handle the guest exception, and we handle it by 
queuing it right back.


Of course, we need to find out why kvm_queue_exception() is broken.  It 
probably needs the same hacky treatment as vmx_inject_irq() for real 
mode.  Eventually I'd like to inject real mode interrupts by writing the 
stack frame, but currently this is diffcult as everything happens in 
interrupts disabled context on the host.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2008-07-13 10:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-10 15:47 [Regression] kvm-userspace: VM freezes after booting FreeDOS Mohammed Gamal
2008-07-10 15:48 ` Mohammed Gamal
2008-07-10 16:31 ` Anthony Liguori
2008-07-10 19:52   ` Mohammed Gamal
2008-07-10 20:02     ` Anthony Liguori
2008-07-10 20:32       ` Mohammed Gamal
2008-07-10 20:33         ` Mohammed Gamal
2008-07-10 21:22         ` Jan Kiszka
2008-07-10 22:59           ` Mohammed Gamal
2008-07-11 10:53             ` Jan Kiszka
2008-07-11 14:55               ` Mohammed Gamal
2008-07-12 11:19                 ` Jan Kiszka
2008-07-13  7:54                   ` Avi Kivity
2008-07-13  9:09                     ` Jan Kiszka
2008-07-13  9:26                       ` Mohammed Gamal
2008-07-13 10:08                         ` Avi Kivity [this message]
2008-07-13  9:55                       ` 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=4879D432.6030104@qumranet.com \
    --to=avi@qumranet.com \
    --cc=anthony@codemonkey.ws \
    --cc=jan.kiszka@siemens.com \
    --cc=jan.kiszka@web.de \
    --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