From: Bernhard Kauer <kauer@os.inf.tu-dresden.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Patch: generate a DBF when a GPF could not be delivered on x86
Date: Wed, 28 Mar 2007 14:39:31 +0200 [thread overview]
Message-ID: <20070328123931.GA24080@silo.inf.tu-dresden.de> (raw)
In-Reply-To: <460A23BD.8080605@softax.com.pl>
On Wed, Mar 28, 2007 at 10:13:49AM +0200, Sebastian Kaliszewski wrote:
> Bernhard Kauer wrote:
> >Qemu does not generate a double fault (DBF) on x86, if a general protection
> >fault could not be delivered. Instead it hangs in a loop.
> >
> >The patch fix this bug by checking whether we are already in a GPF
> >exception.
>
> If you're at it, maybe add triple fault handling (ie exception if DBF
> handler) -- it should reset CPU.
There are many things missing in the x86 exception handling. For example
the case PF -> PF is also not handled.
Bernhard Kauer
next prev parent reply other threads:[~2007-03-28 12:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 11:40 [Qemu-devel] Patch: generate a DBF when a GPF could not be delivered on x86 Bernhard Kauer
2007-03-28 8:13 ` Sebastian Kaliszewski
2007-03-28 12:39 ` Bernhard Kauer [this message]
2007-03-31 12:14 ` [Qemu-devel] Patch: generate double and triple faults Bernhard Kauer
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=20070328123931.GA24080@silo.inf.tu-dresden.de \
--to=kauer@os.inf.tu-dresden.de \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).