From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Jm8sG-0003QT-S7 for qemu-devel@nongnu.org; Wed, 16 Apr 2008 10:44:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Jm8sG-0003QH-7L for qemu-devel@nongnu.org; Wed, 16 Apr 2008 10:44:36 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Jm8sG-0003QC-15 for qemu-devel@nongnu.org; Wed, 16 Apr 2008 10:44:36 -0400 Received: from yw-out-1718.google.com ([74.125.46.158]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Jm8sF-00077U-Pa for qemu-devel@nongnu.org; Wed, 16 Apr 2008 10:44:35 -0400 Received: by yw-out-1718.google.com with SMTP id 4so1307789ywq.82 for ; Wed, 16 Apr 2008 07:44:28 -0700 (PDT) Message-ID: <480610C9.4040503@codemonkey.ws> Date: Wed, 16 Apr 2008 09:44:25 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH] Reboot CPU on triple fault References: <47EE86E0.4070703@reactos.org> <47F0B445.4030806@suse.de> <4804D254.5040301@siemens.com> <200804151757.05303.paul@codesourcery.com> In-Reply-To: <200804151757.05303.paul@codesourcery.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 Cc: Jan Kiszka Paul Brook wrote: >> + if (env->old_exception == EXCP08_DBLE) { >> + fprintf(stderr, "qemu: warning: triple fault\n"); >> > > 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. > Moreover, it's a standard means of rebooting in the absence of APM or ACPI. See native_machine_emergency_restart() in arch/x86/kernel/reboot.c in Linux. Regards, Anthony Liguori > Paul > > >