qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@suse.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] Reboot CPU on triple fault
Date: Wed, 16 Apr 2008 10:18:59 +0200	[thread overview]
Message-ID: <4805B673.3010200@suse.de> (raw)
In-Reply-To: <4804D254.5040301@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 823 bytes --]

Jan Kiszka schrieb:
> As the same requirement came up here, I worked out the following patch.
> I feel a bit uneasy about it because
> 
>  o I'm unsure if breaking out of the exception loop is OK this way.
> 
>  o including necessary headers fails, mostly due to stdio redefinitions
>    in dyngen-exec.h.
> 
> This patch behaves as it should, but only in one specific test case.
> Feedback is welcome.

This is exactly the behaviour I'd like to have. I still needed a small
change to your patch, though: You shouldn't return 0 from
check_exception, after all it's not a divide error. I'm not sure if
EXCP_HLT is the right thing to return here, but the attached patch works
for me. Without this change it kept hanging in a loop forever writing
more dumps than I ever wanted. ;-)

Signed-off-by: Kevin Wolf <kwolf@suse.de>


[-- Attachment #2: qemu-triple-fault.patch --]
[-- Type: text/x-patch, Size: 1729 bytes --]

Index: dyngen-exec.h
===================================================================
--- dyngen-exec.h	(Revision 4215)
+++ dyngen-exec.h	(Arbeitskopie)
@@ -86,6 +86,7 @@
 extern int fprintf(FILE *, const char *, ...);
 extern int fputs(const char *, FILE *);
 extern int printf(const char *, ...);
+extern FILE *stderr;
 #undef NULL
 #define NULL 0
 
Index: target-i386/helper.c
===================================================================
--- target-i386/helper.c	(Revision 4215)
+++ target-i386/helper.c	(Arbeitskopie)
@@ -1231,6 +1231,8 @@
     }
 }
 
+void qemu_system_reset_request(void);
+
 /*
  * Check nested exceptions and change to double or triple fault if
  * needed. It should only be called, if this is not an interrupt.
@@ -1248,8 +1250,21 @@
         fprintf(logfile, "check_exception old: %x new %x\n",
                 env->old_exception, intno);
 
-    if (env->old_exception == EXCP08_DBLE)
-        cpu_abort(env, "triple fault");
+    if (env->old_exception == EXCP08_DBLE) {
+        fprintf(stderr, "qemu: warning: triple fault\n");
+        if(env->intercept & INTERCEPT_SVM_MASK) {
+            /* most probably the virtual machine should not
+               be shut down but rather caught by the VMM */
+            vmexit(SVM_EXIT_SHUTDOWN, 0);
+        }
+        cpu_dump_state(env, stderr, fprintf, X86_DUMP_FPU | X86_DUMP_CCOP);
+        if (logfile) {
+            fprintf(logfile, "qemu: warning: triple fault\n");
+            cpu_dump_state(env, logfile, fprintf, X86_DUMP_FPU | X86_DUMP_CCOP);
+        }
+        qemu_system_reset_request();
+        return EXCP_HLT;
+    }
 
     if ((first_contributory && second_contributory)
         || (env->old_exception == EXCP0E_PAGE &&

  parent reply	other threads:[~2008-04-16  8:24 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-29 18:13 [Qemu-devel] [PATCH] Reboot CPU on triple fault Hervé Poussineau
2008-03-30  1:36 ` Alexander Graf
2008-03-31  9:52   ` Kevin Wolf
2008-04-15 16:05     ` [Qemu-devel] " Jan Kiszka
2008-04-15 16:57       ` Paul Brook
2008-04-16  8:37         ` Kevin Wolf
2008-04-16  9:23           ` Jamie Lokier
2008-04-16  9:51             ` Antoine Kaufmann
2008-04-16  9:53             ` Kevin Wolf
2008-04-16 10:17               ` Michal Schulz
2008-04-16 10:25                 ` Michal Schulz
2008-04-16 12:08                 ` Kevin Wolf
2008-04-16 10:22               ` Jan Kiszka
2008-04-16 11:34               ` Jamie Lokier
2008-04-16 14:44         ` Anthony Liguori
2008-04-16  8:18       ` Kevin Wolf [this message]
2008-04-16 12:02         ` Jan Kiszka
2008-04-16 12:09           ` Avi Kivity
2008-04-16 12:36           ` Kevin Wolf
2008-04-16 12:57             ` Jamie Lokier
2008-04-16 12:44       ` [Qemu-devel] [PATCH] x86: Reboot CPU on triple fault - Version 3 Jan Kiszka
2008-04-16 13:35         ` [Qemu-devel] [PATCH] x86: Reboot CPU on triple fault - Version 4 Kevin Wolf
2008-04-16 14:18           ` [Qemu-devel] " Jan Kiszka
2008-04-16 14:33             ` [Qemu-devel] [PATCH] x86: Reboot CPU on triple fault - Version 5 Kevin Wolf
2008-04-16 14:57               ` [Qemu-devel] [PATCH] x86: Reboot CPU on triple fault - Version 6 Kevin Wolf
2008-04-17  9:52                 ` [Qemu-devel] " Jan Kiszka
2008-04-18 14:06                 ` [Qemu-devel] " Anthony Liguori
2008-04-21 11:53                   ` Kevin Wolf
2008-05-26 14:46                     ` [Qemu-devel] " Jan Kiszka
2008-05-27 16:01                       ` [Qemu-devel] [PATCH] x86: Reboot CPU on triple fault - Version 8 Jan Kiszka
2008-05-27 16:17                         ` [Qemu-devel] " Jan Kiszka
2008-04-16 14:37           ` [Qemu-devel] Re: [PATCH] x86: Reboot CPU on triple fault - Version 4 Anthony Liguori
2008-04-17  8:07             ` Jan Kiszka
2008-04-17 12:49               ` Anthony Liguori
2008-04-17 14:10                 ` Jan Kiszka
2008-04-17 18:30                   ` Anthony Liguori
2008-04-17 19:24                     ` Jan Kiszka
2008-04-18  8:38                     ` Kevin Wolf
2008-04-18 14:08                       ` Anthony Liguori
2008-04-21  9:37                         ` Kevin Wolf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4805B673.3010200@suse.de \
    --to=kwolf@suse.de \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).