From: Don Zickus <dzickus@redhat.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: akpm@linux-foundation.org, x86@kernel.org, davem@davemloft.net,
sparclinux@vger.kernel.org, mguzik@redhat.com,
Aaron Tomlin <atomlin@redhat.com>,
Don Zickus <dzickus@redhat.com>
Subject: [PATCH 1/4 v2] nmi: Provide the option to issue an NMI back trace to every cpu but current
Date: Fri, 4 Apr 2014 16:47:07 -0400 [thread overview]
Message-ID: <1396644430-70649-2-git-send-email-dzickus@redhat.com> (raw)
In-Reply-To: <1396644430-70649-1-git-send-email-dzickus@redhat.com>
From: Aaron Tomlin <atomlin@redhat.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@redhat.com>
Signed-off-by: Don Zickus <dzickus@redhat.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
next prev parent reply other threads:[~2014-04-04 20:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-04 20:47 [PATCH 0/4 V2] Print traces on softlockups Don Zickus
2014-04-04 20:47 ` Don Zickus [this message]
2014-04-04 20:47 ` [PATCH 2/4 v2] x86, nmi: Add more flexible NMI back trace support Don Zickus
2014-04-04 20:47 ` [PATCH 3/4 v2] sparc64, " Don Zickus
2014-04-04 20:53 ` David Miller
2014-04-04 20:47 ` [PATCH 4/4 v2] watchdog: Printing traces for all cpus on lockup detection Don Zickus
[not found] <20140415075650.GG2195@atomlin.usersys.redhat.com>
[not found] ` <20140415170202.GA7948@redhat.com>
[not found] ` <20140415172649.GA10152@redhat.com>
[not found] ` <20140421132100.GW8488@redhat.com>
2014-04-21 13:41 ` [PATCH 1/4 v2] nmi: Provide the option to issue an NMI back trace to every cpu but current Oleg Nesterov
2014-04-21 15:47 ` Don Zickus
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=1396644430-70649-2-git-send-email-dzickus@redhat.com \
--to=dzickus@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=atomlin@redhat.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mguzik@redhat.com \
--cc=sparclinux@vger.kernel.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).