From: Keith Owens <kaos@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: [patch] 2.6.3 sync unwind code with 2.4.25
Date: Mon, 23 Feb 2004 03:46:34 +0000 [thread overview]
Message-ID: <4545.1077507994@kao2.melbourne.sgi.com> (raw)
The unwind code in 2.6.3 is missing a debug patch. This patch is in
2.4.25 and makes it much easier to diagnose unwind problems. printk
output does not appear when in_interrupt(), kdb_printf output does.
This brings 2.6.3 unwind closer to 2.4.25.
Index: 3.1/arch/ia64/kernel/unwind.c
--- 3.1/arch/ia64/kernel/unwind.c Sun, 08 Feb 2004 22:59:56 +1100 kaos (linux-2.6/Z/c/10_unwind.c 1.1.1.2 644)
+++ 3.1(w)/arch/ia64/kernel/unwind.c Mon, 23 Feb 2004 14:44:05 +1100 kaos (linux-2.6/Z/c/10_unwind.c 1.1.1.2 644)
@@ -60,9 +60,16 @@
#ifdef UNW_DEBUG
static unsigned int unw_debug_level = UNW_DEBUG;
-# define UNW_DEBUG_ON(n) unw_debug_level >= n
- /* Do not code a printk level, not all debug lines end in newline */
-# define UNW_DPRINT(n, ...) if (UNW_DEBUG_ON(n)) printk(__VA_ARGS__)
+# ifdef CONFIG_KDB
+# include <linux/kdb.h>
+# define UNW_DEBUG_ON(n) (unw_debug_level >= n && !KDB_IS_RUNNING())
+# define UNW_DPRINT(n, ...) if (UNW_DEBUG_ON(n)) kdb_printf(__VA_ARGS__)
+# else /* !CONFIG_KDB */
+# define UNW_DEBUG_ON(n) unw_debug_level >= n
+ /* Do not code a printk level, not all debug lines end in newline */
+# define UNW_DPRINT(n, ...) if (UNW_DEBUG_ON(n)) printk(__VA_ARGS__)
+# endif /* CONFIG_KDB */
+# undef inline
# define inline
#else /* !UNW_DEBUG */
# define UNW_DEBUG_ON(n) 0
next reply other threads:[~2004-02-23 3:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 3:46 Keith Owens [this message]
2004-02-23 20:07 ` [patch] 2.6.3 sync unwind code with 2.4.25 David Mosberger
2004-02-23 21:38 ` Keith Owens
2004-02-23 21:47 ` David Mosberger
2004-02-23 23:09 ` David Mosberger
2004-02-23 23:28 ` Keith Owens
2004-02-23 23:34 ` David Mosberger
2004-02-23 23:53 ` Keith Owens
2004-02-24 0:02 ` David Mosberger
2004-02-24 0:03 ` David Mosberger
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=4545.1077507994@kao2.melbourne.sgi.com \
--to=kaos@sgi.com \
--cc=linux-ia64@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