public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Mohammed Gamal <m.gamal005@gmail.com>,
	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 12:55:38 +0300	[thread overview]
Message-ID: <4879D11A.9090900@qumranet.com> (raw)
In-Reply-To: <4879C636.30003@web.de>

Jan Kiszka wrote:
>>>     
>>>       
>> But it seems the best thing to do is not to trap #DB in
>> update_exception_bitmap()?
>>     
>
> Was my first idea as well. I do not understand what is going on there,
> but when I simply exclude #DB from the exception bitmap in real mode,
> the problem pops up again: #GP on the instruction that should raise the #DB.
>
>   

Right.  The docs say that a #DB (like all exceptions) will trap to the 
protected mode handler through the #GP exception.

So, we do need kvm_queue_exception.

>>> /me now wonders if there are not even more exceptions that have to be
>>> forwarded. Right now we catch them all, but I did not find some path
>>> via which actual ones are pushed to the guest.
>>>       
>> Looks like update_exception_bitmap() assumes none.  From a cursory look,
>> seems like #DE (divide error), #DB, #BP (Breakpoint), #OF (overflow),
>> #BR (range check) all need to be passed to the guest.
>>     
>
> Hmm, unless KVM did something to fix up some exception, shouldn't all of
> them be passed?
>   

Yes, they should.  But it can't be done using the exception bitmap.

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


      parent reply	other threads:[~2008-07-13  9:55 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
2008-07-13  9:55                       ` 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=4879D11A.9090900@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