From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JmPBU-00079F-CS for qemu-devel@nongnu.org; Thu, 17 Apr 2008 04:09:32 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JmPBT-00078x-6W for qemu-devel@nongnu.org; Thu, 17 Apr 2008 04:09:32 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JmPBT-00078u-2s for qemu-devel@nongnu.org; Thu, 17 Apr 2008 04:09:31 -0400 Received: from mx20.gnu.org ([199.232.41.8]) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1JmPBS-0008JS-Jr for qemu-devel@nongnu.org; Thu, 17 Apr 2008 04:09:30 -0400 Received: from lizzard.sbs.de ([194.138.37.39]) by mx20.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JmPBR-0000Zg-1b for qemu-devel@nongnu.org; Thu, 17 Apr 2008 04:09:29 -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 m3H87Guj030992 for ; Thu, 17 Apr 2008 10:07:16 +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 m3H87FBv004793 for ; Thu, 17 Apr 2008 10:07:15 +0200 Message-ID: <48070533.5060405@siemens.com> Date: Thu, 17 Apr 2008 10:07:15 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <47EE86E0.4070703@reactos.org> <9C7667CB-2CF0-4AC0-843B-6EF442196CAC@csgraf.de> <47F0B445.4030806@suse.de> <4804D254.5040301@siemens.com> <4805F4B0.5020802@siemens.com> <4806009E.8060407@suse.de> <48060F42.3080709@codemonkey.ws> In-Reply-To: <48060F42.3080709@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH] x86: Reboot CPU on triple fault - Version 4 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 Anthony Liguori wrote: > Kevin Wolf wrote: >> And another version which implements the -d cpu_reset suggested by >> Jamie. Extending -d is probably better than introducing a completely new >> option. >> >> Signed-off-by: Kevin Wolf >> > > Why is it so important to log triple faults? Printing something to > stderr instead of logfile is just wrong. > > What is your use-case? I think you've got the wrong solution to the > problem and I can't find an adequate description of the problem your > trying to solve in this thread. You may not always sit next to your VM when it decides to reboot due to a _real_ problem that caused a triple fault. Jan -- Siemens AG, Corporate Technology, CT SE 2 Corporate Competence Center Embedded Linux