[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1398179848-197479-2-git-send-email-dzickus@redhat.com>
Date: Tue, 22 Apr 2014 11:17:25 -0400
From: Don Zickus <dzickus@...hat.com>
To: LKML <linux-kernel@...r.kernel.org>
Cc: akpm@...ux-foundation.org, x86@...nel.org, davem@...emloft.net,
sparclinux@...r.kernel.org, mguzik@...hat.com,
Aaron Tomlin <atomlin@...hat.com>,
Don Zickus <dzickus@...hat.com>
Subject: [PATCH 1/4 v3] nmi: Provide the option to issue an NMI back trace to every cpu but current
From: Aaron Tomlin <atomlin@...hat.com>
Some times it is preferred not to use the
trigger_all_cpu_backtrace() routine when one wants
to avoid capturing a back trace for current.
For instance if one was previously captured
recently.
This patch provides a new routine namely
trigger_allbutself_cpu_backtrace() which offers
the flexibility to issue an NMI to every cpu but
current and capture a back trace accordingly.
[Added stub in #else clause - dcz]
Signed-off-by: Aaron Tomlin <atomlin@...hat.com>
Signed-off-by: Don Zickus <dzickus@...hat.com>
---
include/linux/nmi.h | 11 ++++++++++-
1 files changed, 10 insertions(+), 1 deletions(-)
diff --git a/include/linux/nmi.h b/include/linux/nmi.h
index 6a45fb5..a17ab63 100644
--- a/include/linux/nmi.h
+++ b/include/linux/nmi.h
@@ -32,15 +32,24 @@ static inline void touch_nmi_watchdog(void)
#ifdef arch_trigger_all_cpu_backtrace
static inline bool trigger_all_cpu_backtrace(void)
{
- arch_trigger_all_cpu_backtrace();
+ arch_trigger_all_cpu_backtrace(true);
return true;
}
+static inline bool trigger_allbutself_cpu_backtrace(void)
+{
+ arch_trigger_all_cpu_backtrace(false);
+ return true;
+}
#else
static inline bool trigger_all_cpu_backtrace(void)
{
return false;
}
+static inline bool trigger_allbutself_cpu_backtrace(void)
+{
+ return false;
+}
#endif
#ifdef CONFIG_LOCKUP_DETECTOR
--
1.7.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists