From: "Wink Saville" <wink@saville.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH 7/7] Add trec_snapshot and trec_print_snapshot in panic()
Date: Tue, 20 Mar 2007 23:54:10 -0700 [thread overview]
Message-ID: <d4cf37a60703202354l648e08fauecb730c2de46fd41@mail.gmail.com> (raw)
Signed-off-by: Wink Saville <wink@saville.com>
---
kernel/panic.c | 12 ++++++++++++
1 files changed, 12 insertions(+), 0 deletions(-)
diff --git a/kernel/panic.c b/kernel/panic.c
index 623d182..64a047e 100644
--- a/kernel/panic.c
+++ b/kernel/panic.c
@@ -20,6 +20,10 @@
#include <linux/kexec.h>
#include <linux/debug_locks.h>
+#ifdef CONFIG_TREC
+#include <linux/trec.h>
+#endif
+
int panic_on_oops;
int tainted;
static int pause_on_oops;
@@ -66,6 +70,10 @@ NORET_TYPE void panic(const char * fmt, ...)
unsigned long caller = (unsigned long) __builtin_return_address(0);
#endif
+#ifdef CONFIG_TREC
+ trec_snapshot();
+#endif
+
/*
* It's possible to come here directly from a panic-assertion and not
* have preempt disabled. Some functions called from here want
@@ -96,6 +104,10 @@ NORET_TYPE void panic(const char * fmt, ...)
smp_send_stop();
#endif
+#ifdef CONFIG_TREC
+ trec_print_snapshot();
+#endif
+
atomic_notifier_call_chain(&panic_notifier_list, 0, buf);
if (!panic_blink)
--
1.5.0.rc2
reply other threads:[~2007-03-21 6:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=d4cf37a60703202354l648e08fauecb730c2de46fd41@mail.gmail.com \
--to=wink@saville.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®