summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorJason Wessel <jason.wessel@windriver.com>2011-07-28 17:42:23 (GMT)
committerScott Wood <scottwood@freescale.com>2015-02-13 22:20:59 (GMT)
commit8d627274e496041f381a09ef1c0fa166ae3693d9 (patch)
treeddda95a3908aaa2038c49a5ffe14f07c6dca6b15 /include
parent3be1ad041890455b3d91bfb728d2c0112f36a724 (diff)
downloadlinux-fsl-qoriq-8d627274e496041f381a09ef1c0fa166ae3693d9.tar.xz
kgdb/serial: Short term workaround
On 07/27/2011 04:37 PM, Thomas Gleixner wrote: > - KGDB (not yet disabled) is reportedly unusable on -rt right now due > to missing hacks in the console locking which I dropped on purpose. > To work around this in the short term you can use this patch, in addition to the clocksource watchdog patch that Thomas brewed up. Comments are welcome of course. Ultimately the right solution is to change separation between the console and the HW to have a polled mode + work queue so as not to introduce any kind of latency. Thanks, Jason.
Diffstat (limited to 'include')
-rw-r--r--include/linux/kdb.h3
1 files changed, 2 insertions, 1 deletions
diff --git a/include/linux/kdb.h b/include/linux/kdb.h
index 7f6fe6e..680ad23 100644
--- a/include/linux/kdb.h
+++ b/include/linux/kdb.h
@@ -115,7 +115,7 @@ extern int kdb_trap_printk;
extern __printf(1, 0) int vkdb_printf(const char *fmt, va_list args);
extern __printf(1, 2) int kdb_printf(const char *, ...);
typedef __printf(1, 2) int (*kdb_printf_t)(const char *, ...);
-
+#define in_kdb_printk() (kdb_trap_printk)
extern void kdb_init(int level);
/* Access to kdb specific polling devices */
@@ -150,6 +150,7 @@ extern int kdb_register_repeat(char *, kdb_func_t, char *, char *,
extern int kdb_unregister(char *);
#else /* ! CONFIG_KGDB_KDB */
static inline __printf(1, 2) int kdb_printf(const char *fmt, ...) { return 0; }
+#define in_kdb_printk() (0)
static inline void kdb_init(int level) {}
static inline int kdb_register(char *cmd, kdb_func_t func, char *usage,
char *help, short minlen) { return 0; }