From: Jan Kiszka <jan.kiszka@siemens.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] x86: Reboot CPU on triple fault - Version 4
Date: Wed, 16 Apr 2008 16:18:52 +0200 [thread overview]
Message-ID: <48060ACC.2020309@siemens.com> (raw)
In-Reply-To: <4806009E.8060407@suse.de>
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.
Sounds good.
>
> Signed-off-by: Kevin Wolf <kwolf@suse.de>
>
> 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: exec.c
> ===================================================================
> --- exec.c (Revision 4215)
> +++ exec.c (Arbeitskopie)
> @@ -1259,6 +1259,8 @@
> #ifdef TARGET_I386
> { CPU_LOG_PCALL, "pcall",
> "show protected mode far calls/returns/exceptions" },
> + { CPU_LOG_RESET, "cpu_reset",
> + "show CPU state before CPU resets" },
> #endif
> #ifdef DEBUG_IOPORT
> { CPU_LOG_IOPORT, "ioport",
> Index: target-i386/helper.c
> ===================================================================
> --- target-i386/helper.c (Revision 4215)
> +++ target-i386/helper.c (Arbeitskopie)
> @@ -1231,6 +1231,10 @@
> }
> }
>
> +/* This should come from sysemu.h - if we could include it here... */
> +void qemu_system_reset_request(void);
> +extern int warn_on_triple_fault;
The latter is now obsolete.
> +
> /*
> * 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 +1252,19 @@
> 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) {
> + 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);
> + }
> + if (loglevel & CPU_LOG_RESET) {
> + fprintf(stderr, "qemu: warning: triple fault\n");
Does 'loglevel' manage dumping to stderr as well? I don't think so. To
remain consistent, the line above should probably be removed.
> + fprintf(logfile, "qemu: warning: triple fault\n");
> + }
> + qemu_system_reset_request();
> + return EXCP_HLT;
> + }
>
> if ((first_contributory && second_contributory)
> || (env->old_exception == EXCP0E_PAGE &&
> Index: target-i386/helper2.c
> ===================================================================
> --- target-i386/helper2.c (Revision 4215)
> +++ target-i386/helper2.c (Arbeitskopie)
> @@ -362,6 +362,10 @@
> void cpu_reset(CPUX86State *env)
> {
> int i;
> +
> + if (loglevel & CPU_LOG_RESET) {
> + cpu_dump_state(env, logfile, fprintf, X86_DUMP_FPU | X86_DUMP_CCOP);
> + }
>
> memset(env, 0, offsetof(CPUX86State, breakpoints));
>
> Index: cpu-all.h
> ===================================================================
> --- cpu-all.h (Revision 4215)
> +++ cpu-all.h (Arbeitskopie)
> @@ -779,6 +779,7 @@
> #define CPU_LOG_PCALL (1 << 6)
> #define CPU_LOG_IOPORT (1 << 7)
> #define CPU_LOG_TB_CPU (1 << 8)
> +#define CPU_LOG_RESET (1 << 9)
>
> /* define log items */
> typedef struct CPULogItem {
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2008-04-16 14:19 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
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 ` Jan Kiszka [this message]
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=48060ACC.2020309@siemens.com \
--to=jan.kiszka@siemens.com \
--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).