From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Keir Fraser <keir@xen.org>, Jan Beulich <jbeulich@suse.com>
Subject: [PATCH] kexec/noreboot: Don't kexec_crash() if noreboot has been requested.
Date: Fri, 7 Sep 2012 14:05:19 +0100 [thread overview]
Message-ID: <5049F10F.5010801@citrix.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 205 bytes --]
This issue came up when debugging pcpu linked list corruption (patches
for that issue to follow).
--
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com
[-- Attachment #2: noreboot.patch --]
[-- Type: text/x-patch, Size: 840 bytes --]
# HG changeset patch
# Parent 1126b3079bef37e1bb5a97b90c14a51d4e1c91c3
kexec/noreboot: Don't kexec_crash() if noreboot has been requested.
The noreboot option is for debugging, to be able to see the dying output. To
that end, continuing and possibly booting into the crash kernel defeats one of
the purposes of noreboot.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
diff -r 1126b3079bef xen/drivers/char/console.c
--- a/xen/drivers/char/console.c
+++ b/xen/drivers/char/console.c
@@ -963,16 +963,15 @@ void panic(const char *fmt, ...)
debugger_trap_immediate();
-#ifdef CONFIG_KEXEC
- kexec_crash();
-#endif
-
if ( opt_noreboot )
{
machine_halt();
}
else
{
+#ifdef CONFIG_KEXEC
+ kexec_crash();
+#endif
watchdog_disable();
machine_restart(5000);
}
[-- Attachment #3: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2012-09-07 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-07 13:05 Andrew Cooper [this message]
2012-09-07 13:16 ` [PATCH] kexec/noreboot: Don't kexec_crash() if noreboot has been requested Jan Beulich
2012-09-07 13:28 ` Andrew Cooper
2012-09-07 15:03 ` Keir Fraser
2012-09-07 15:42 ` Andrew Cooper
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=5049F10F.5010801@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xen.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).