From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jm3rn-0000ML-TH for qemu-devel@nongnu.org; Wed, 16 Apr 2008 05:23:48 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jm3rm-0000Kp-0G for qemu-devel@nongnu.org; Wed, 16 Apr 2008 05:23:47 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jm3rl-0000KS-FL for qemu-devel@nongnu.org; Wed, 16 Apr 2008 05:23:45 -0400 Received: from mail2.shareable.org ([80.68.89.115]) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Jm3rl-0008CE-5a for qemu-devel@nongnu.org; Wed, 16 Apr 2008 05:23:45 -0400 Received: from jamie by mail2.shareable.org with local (Exim 4.63) (envelope-from ) id 1Jm3rh-0007Gp-47 for qemu-devel@nongnu.org; Wed, 16 Apr 2008 10:23:41 +0100 Date: Wed, 16 Apr 2008 10:23:40 +0100 From: Jamie Lokier Subject: Re: [Qemu-devel] Re: [PATCH] Reboot CPU on triple fault Message-ID: <20080416092340.GA27898@shareable.org> References: <47EE86E0.4070703@reactos.org> <47F0B445.4030806@suse.de> <4804D254.5040301@siemens.com> <200804151757.05303.paul@codesourcery.com> <4805BAB0.1030707@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4805BAB0.1030707@suse.de> 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: > > IMHO There's no reason to print a message to stderr. This is all > > well defined behavior, and the accepted way of exiting from 286 > > protected mode. > > How many users does qemu have who need triple faults to exit from 286 > Protected Mode? Not many, only those users running old MS-DOS apps / OSes. > And how many users does it have who don't use triple > faults (yes, it's called a fault, not a PM exiting feature) Faults don't mean errors. Think about page faults. > 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. -- Jamie