From: Jason Wessel <jason.wessel@windriver.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org,
kgdb-bugreport@lists.sourceforge.net,
Jason Wessel <jason.wessel@windriver.com>
Subject: [PATCH 20/25] kgdb: Add the ability to schedule a breakpoint via a tasklet
Date: Tue, 18 May 2010 20:39:30 -0500 [thread overview]
Message-ID: <1274233175-3675-21-git-send-email-jason.wessel@windriver.com> (raw)
In-Reply-To: <1274233175-3675-1-git-send-email-jason.wessel@windriver.com>
Some kgdb I/O modules require the ability to create a breakpoint
tasklet, such as kgdboc and external modules such as kgdboe. The
breakpoint tasklet is used as an asynchronous entry point into the
debugger which will have a different function scope than the current
execution path where it might not be safe to have an inline
breakpoint. This is true of some of the kgdb I/O drivers which share
code with kgdb and rest of the kernel users.
Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
---
include/linux/kgdb.h | 1 +
kernel/debug/debug_core.c | 26 ++++++++++++++++++++++++++
2 files changed, 27 insertions(+), 0 deletions(-)
diff --git a/include/linux/kgdb.h b/include/linux/kgdb.h
index 19d1b29..ee007ea 100644
--- a/include/linux/kgdb.h
+++ b/include/linux/kgdb.h
@@ -271,6 +271,7 @@ extern int kgdb_mem2hex(char *mem, char *buf, int count);
extern int kgdb_hex2mem(char *buf, char *mem, int count);
extern int kgdb_isremovedbreak(unsigned long addr);
+extern void kgdb_schedule_breakpoint(void);
extern int
kgdb_handle_exception(int ex_vector, int signo, int err_code,
diff --git a/kernel/debug/debug_core.c b/kernel/debug/debug_core.c
index 375e42f..fff5901 100644
--- a/kernel/debug/debug_core.c
+++ b/kernel/debug/debug_core.c
@@ -114,6 +114,7 @@ EXPORT_SYMBOL_GPL(kgdb_active);
*/
static atomic_t passive_cpu_wait[NR_CPUS];
static atomic_t cpu_in_kgdb[NR_CPUS];
+static atomic_t kgdb_break_tasklet_var;
atomic_t kgdb_setting_breakpoint;
struct task_struct *kgdb_usethread;
@@ -789,6 +790,31 @@ static void kgdb_unregister_callbacks(void)
}
}
+/*
+ * There are times a tasklet needs to be used vs a compiled in
+ * break point so as to cause an exception outside a kgdb I/O module,
+ * such as is the case with kgdboe, where calling a breakpoint in the
+ * I/O driver itself would be fatal.
+ */
+static void kgdb_tasklet_bpt(unsigned long ing)
+{
+ kgdb_breakpoint();
+ atomic_set(&kgdb_break_tasklet_var, 0);
+}
+
+static DECLARE_TASKLET(kgdb_tasklet_breakpoint, kgdb_tasklet_bpt, 0);
+
+void kgdb_schedule_breakpoint(void)
+{
+ if (atomic_read(&kgdb_break_tasklet_var) ||
+ atomic_read(&kgdb_active) != -1 ||
+ atomic_read(&kgdb_setting_breakpoint))
+ return;
+ atomic_inc(&kgdb_break_tasklet_var);
+ tasklet_schedule(&kgdb_tasklet_breakpoint);
+}
+EXPORT_SYMBOL_GPL(kgdb_schedule_breakpoint);
+
static void kgdb_initial_breakpoint(void)
{
kgdb_break_asap = 0;
--
1.6.3.3
next prev parent reply other threads:[~2010-05-19 1:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 1:39 [GIT PULL] kdb / early debug (1 of 2) for 2.6.35 Jason Wessel
2010-05-19 1:39 ` [PATCH 01/25] Move kernel/kgdb.c to kernel/debug/debug_core.c Jason Wessel
2010-05-19 1:39 ` [PATCH 02/25] Separate the gdbstub from the debug core Jason Wessel
2010-05-19 1:39 ` [PATCH 03/25] MAINTAINERS: update kgdb, and debug_core info Jason Wessel
2010-05-19 1:39 ` [PATCH 04/25] kgdb,sparc: Add in kgdb_arch_set_pc for sparc Jason Wessel
2010-05-19 1:39 ` [PATCH 05/25] kgdb,sh: update superh kgdb exception handling Jason Wessel
2010-05-19 1:39 ` [PATCH 06/25] kgdb,blackfin: Add in kgdb_arch_set_pc for blackfin Jason Wessel
2010-05-19 1:39 ` [PATCH 07/25] kdb: core for kgdb back end (1 of 2) Jason Wessel
2010-05-19 1:39 ` [PATCH 08/25] kdb: core for kgdb back end (2 " Jason Wessel
2010-05-19 1:39 ` [PATCH 09/25] kgdb: core changes to support kdb Jason Wessel
2010-05-19 1:39 ` [PATCH 10/25] kgdb,8250,pl011: Return immediately from console poll Jason Wessel
2010-05-19 1:39 ` [PATCH 11/25] sh,sh-sci: Use NO_POLL_CHAR in the SCIF polled console code Jason Wessel
2010-05-19 1:39 ` [PATCH 12/25] sparc,sunzilog: Add console polling support for sunzilog serial driver Jason Wessel
2010-05-19 1:39 ` [PATCH 13/25] kgdb: gdb "monitor" -> kdb passthrough Jason Wessel
2010-05-19 1:39 ` [PATCH 14/25] kgdboc,keyboard: Keyboard driver for kdb with kgdb Jason Wessel
2010-05-19 1:39 ` [PATCH 15/25] kgdb,docs: Update the kgdb docs to include kdb Jason Wessel
2010-05-19 1:39 ` [PATCH 16/25] kgdb: remove post_primary_code references Jason Wessel
2010-05-19 1:39 ` [PATCH 17/25] x86,kgdb: Add low level debug hook Jason Wessel
2010-05-19 1:39 ` [PATCH 18/25] powerpc,kgdb: Introduce low level trap catching Jason Wessel
2010-05-19 1:39 ` [PATCH 19/25] mips,kgdb: kdb low level trap catch and stack trace Jason Wessel
2010-05-19 1:39 ` Jason Wessel [this message]
2010-05-19 1:39 ` [PATCH 21/25] kgdboc,kdb: Allow kdb to work on a non open console port Jason Wessel
2010-05-19 1:39 ` [PATCH 22/25] printk,kdb: capture printk() when in kdb shell Jason Wessel
2010-05-19 1:39 ` [PATCH 23/25] debug_core,kdb: Allow the debug core to process a recursive debug entry Jason Wessel
2010-05-19 1:39 ` [PATCH 24/25] MAINTAINERS: update kgdb, kdb, and debug_core info Jason Wessel
2010-05-19 1:39 ` [PATCH 25/25] kdb,debug_core: Allow the debug core to receive a panic notification Jason Wessel
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=1274233175-3675-21-git-send-email-jason.wessel@windriver.com \
--to=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®