From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jm4mX-0008Kd-Cu for qemu-devel@nongnu.org; Wed, 16 Apr 2008 06:22:25 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jm4mT-0008JN-I1 for qemu-devel@nongnu.org; Wed, 16 Apr 2008 06:22:23 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jm4mT-0008JK-Bv for qemu-devel@nongnu.org; Wed, 16 Apr 2008 06:22:21 -0400 Received: from lizzard.sbs.de ([194.138.37.39]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Jm4mS-0003Q3-Sk for qemu-devel@nongnu.org; Wed, 16 Apr 2008 06:22:21 -0400 Received: from mail2.sbs.de (localhost [127.0.0.1]) by lizzard.sbs.de (8.12.11.20060308/8.12.11) with ESMTP id m3GAMIge029173 for ; Wed, 16 Apr 2008 12:22:18 +0200 Received: from [139.21.95.227] (mchn012c.mchh.siemens.de [139.21.95.227] (may be forged)) by mail2.sbs.de (8.12.11.20060308/8.12.11) with ESMTP id m3GAMIF4015004 for ; Wed, 16 Apr 2008 12:22:18 +0200 Message-ID: <4805D35A.302@siemens.com> Date: Wed, 16 Apr 2008 12:22:18 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <47EE86E0.4070703@reactos.org> <47F0B445.4030806@suse.de> <4804D254.5040301@siemens.com> <200804151757.05303.paul@codesourcery.com> <4805BAB0.1030707@suse.de> <20080416092340.GA27898@shareable.org> <4805CC9B.7050809@suse.de> In-Reply-To: <4805CC9B.7050809@suse.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH] Reboot CPU on triple fault 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 Kevin Wolf wrote: > Jamie Lokier schrieb: >> Kevin Wolf wrote: >>> And honestly, a message on stderr really shouldn't hurt those 286 folks. >> For old MS-DOS apps / OSes, I have the impression this can happen >> hundreds of times per second. It's part of task context switching and >> BIOS calls. > > I have to admit that I'm all but an 286 PM expert. What exactly is a > triple fault doing there? If it leads to a reset as implemented here, I > can hardly imagine that it is of much use in regular context switching. According to my current information, the triple fault will make the processor issue a shutdown cycle on its external bus. This is obviously detected by many PC boards, which then issue a hard reset. Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux