From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HWXTh-0003yW-EA for qemu-devel@nongnu.org; Wed, 28 Mar 2007 08:42:13 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HWXTf-0003yI-5S for qemu-devel@nongnu.org; Wed, 28 Mar 2007 08:42:12 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HWXTf-0003yF-03 for qemu-devel@nongnu.org; Wed, 28 Mar 2007 07:42:11 -0500 Received: from os.inf.tu-dresden.de ([141.76.48.99]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1HWXRB-0003HI-E4 for qemu-devel@nongnu.org; Wed, 28 Mar 2007 08:39:37 -0400 Received: from silo.inf.tu-dresden.de ([141.76.48.100]) by os.inf.tu-dresden.de with esmtps (TLSv1:AES256-SHA:256) (Exim 4.66) id 1HWXR7-0004KP-RY for qemu-devel@nongnu.org; Wed, 28 Mar 2007 14:39:33 +0200 Received: from kauer by silo.inf.tu-dresden.de with local (Exim 4.50) id 1HWXR5-0006Gb-9B for qemu-devel@nongnu.org; Wed, 28 Mar 2007 14:39:31 +0200 Date: Wed, 28 Mar 2007 14:39:31 +0200 Subject: Re: [Qemu-devel] Patch: generate a DBF when a GPF could not be delivered on x86 Message-ID: <20070328123931.GA24080@silo.inf.tu-dresden.de> References: <20070327114036.GD32622@silo.inf.tu-dresden.de> <460A23BD.8080605@softax.com.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <460A23BD.8080605@softax.com.pl> From: Bernhard Kauer Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org 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