From: Jeffrey Merkey <jeffmerkey@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: davem@davemloft.net, linux.mdb@gmail.com, sparclinux@vger.kernel.org
Subject: [PATCH 30/31] Add debugger entry points for SPARC
Date: Thu, 28 Jan 2016 19:47:48 +0000 [thread overview]
Message-ID: <1454010468-29651-1-git-send-email-jeffmerkey@gmail.com> (raw)
This patch series adds an export which can be set by system debuggers to
direct the hard lockup and soft lockup detector to trigger a breakpoint
exception and enter a debugger if one is active. It is assumed that if
someone sets this variable, then an breakpoint handler of some sort will
be actively loaded or registered via the notify die handler chain.
This addition is extremely useful for debugging hard and soft lockups
real time and quickly from a console debugger.
Signed-off-by: Jeffrey Merkey <jeffmerkey@gmail.com>
---
arch/sparc/include/asm/kdebug.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/sparc/include/asm/kdebug.h b/arch/sparc/include/asm/kdebug.h
index 8d12581..a4b78d3 100644
--- a/arch/sparc/include/asm/kdebug.h
+++ b/arch/sparc/include/asm/kdebug.h
@@ -5,4 +5,9 @@
#else
#include <asm/kdebug_32.h>
#endif
+
+static inline void arch_breakpoint(void)
+{
+ asm("ta $0x7d");
+}
#endif
--
1.8.3.1
WARNING: multiple messages have this Message-ID (diff)
From: Jeffrey Merkey <jeffmerkey@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: davem@davemloft.net, linux.mdb@gmail.com, sparclinux@vger.kernel.org
Subject: [PATCH 30/31] Add debugger entry points for SPARC
Date: Thu, 28 Jan 2016 12:47:48 -0700 [thread overview]
Message-ID: <1454010468-29651-1-git-send-email-jeffmerkey@gmail.com> (raw)
This patch series adds an export which can be set by system debuggers to
direct the hard lockup and soft lockup detector to trigger a breakpoint
exception and enter a debugger if one is active. It is assumed that if
someone sets this variable, then an breakpoint handler of some sort will
be actively loaded or registered via the notify die handler chain.
This addition is extremely useful for debugging hard and soft lockups
real time and quickly from a console debugger.
Signed-off-by: Jeffrey Merkey <jeffmerkey@gmail.com>
---
arch/sparc/include/asm/kdebug.h | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/sparc/include/asm/kdebug.h b/arch/sparc/include/asm/kdebug.h
index 8d12581..a4b78d3 100644
--- a/arch/sparc/include/asm/kdebug.h
+++ b/arch/sparc/include/asm/kdebug.h
@@ -5,4 +5,9 @@
#else
#include <asm/kdebug_32.h>
#endif
+
+static inline void arch_breakpoint(void)
+{
+ asm("ta $0x7d");
+}
#endif
--
1.8.3.1
next reply other threads:[~2016-01-28 19:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 19:47 Jeffrey Merkey [this message]
2016-01-28 19:47 ` [PATCH 30/31] Add debugger entry points for SPARC Jeffrey Merkey
2016-01-28 21:32 ` kbuild test robot
2016-01-28 21:32 ` kbuild test robot
2016-01-28 21:33 ` Sam Ravnborg
2016-01-28 21:33 ` Sam Ravnborg
2016-01-28 21:35 ` Jeffrey Merkey
2016-01-28 21:35 ` Jeffrey Merkey
2016-01-28 21:44 ` kbuild test robot
2016-01-28 21:44 ` kbuild test robot
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=1454010468-29651-1-git-send-email-jeffmerkey@gmail.com \
--to=jeffmerkey@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.mdb@gmail.com \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.