From: Anton Vorontsov <anton.vorontsov@linaro.org>
To: Russell King <linux@arm.linux.org.uk>,
Jason Wessel <jason.wessel@windriver.com>
Cc: "Arve Hjønnevåg" <arve@android.com>,
"Colin Cross" <ccross@android.com>,
"John Stultz" <john.stultz@linaro.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linaro-kernel@lists.linaro.org, patches@linaro.org,
kernel-team@android.com, kgdb-bugreport@lists.sourceforge.net
Subject: [PATCH 5/8] ARM: kgdb_fiq: Implement knocking into KDB via escape command
Date: Fri, 13 Jul 2012 03:16:45 -0700 [thread overview]
Message-ID: <1342174608-22407-5-git-send-email-anton.vorontsov@linaro.org> (raw)
In-Reply-To: <20120713101605.GA16139@lizard>
As Colin Cross noticed, serial ports could be noisy, so occasional
characters once in a while are possible. So, considering the noise
possibility, entering the debugger on any received byte is unacceptable
for production devices.
This changes KGDB FIQ behaviour in a such way so that we have to type the
GDB-protocol "$3#33" command to actually enter the debugger, the kernel
will print the following prompt:
Type $3#33 to enter the debugger.
This is the exactly the same command we use to escape from KGDB to KDB,
so it should be all pretty familiar.
For convenience, there is a kgdb_fiq.knock kernel command line option,
when set to 0, this turns the special command to just a return key
press, so the kernel will be printing this:
Hit <return> to enter the debugger.
Suggested-by: Colin Cross <ccross@android.com>
Signed-off-by: Anton Vorontsov <anton.vorontsov@linaro.org>
---
arch/arm/kernel/kgdb_fiq.c | 48 ++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 48 insertions(+)
diff --git a/arch/arm/kernel/kgdb_fiq.c b/arch/arm/kernel/kgdb_fiq.c
index 7ec9979..5308697 100644
--- a/arch/arm/kernel/kgdb_fiq.c
+++ b/arch/arm/kernel/kgdb_fiq.c
@@ -17,6 +17,7 @@
#include <linux/init.h>
#include <linux/slab.h>
#include <linux/hardirq.h>
+#include <linux/kdb.h>
#include <linux/kgdb.h>
#include <asm/fiq.h>
#include <asm/exception.h>
@@ -25,6 +26,51 @@ static int kgdb_fiq_enabled;
module_param_named(enable, kgdb_fiq_enabled, int, 0600);
MODULE_PARM_DESC(enable, "set to 1 to enable FIQ KGDB");
+static bool kgdb_fiq_knock = 1;
+module_param_named(knock, kgdb_fiq_knock, bool, 0600);
+MODULE_PARM_DESC(knock, "'$3#33' command must be used to enter the debugger");
+
+/*
+ * "Serial ports are often noisy, especially when muxed over another port (we
+ * often use serial over the headset connector). Noise on the async command
+ * line just causes characters that are ignored, on a command line that blocked
+ * execution noise would be catastrophic." -- Colin Cross
+ *
+ * So, this small function implements KGDB/KDB knocking on the serial line: we
+ * won't enter the debugger until we receive a known magic phrase (which is
+ * actually "$3#33", known as "escape to KDB" command. If knocking is disabled,
+ * just pressing the return key is enough to enter the debugger.
+ */
+static bool kgdb_fiq_poll_knock(void)
+{
+ static int n;
+ int c = -1;
+ get_char_func *getc;
+ const char *magic = "$3#33";
+ size_t m = strlen(magic);
+
+ for (getc = &kdb_poll_funcs[0]; *getc; ++getc) {
+ c = (*getc)();
+ if (c >= 0)
+ break;
+ }
+
+ if (!kgdb_fiq_knock && (c == '\r' || c == '\n')) {
+ return 1;
+ } else if (c == magic[n]) {
+ kdb_printf("%c", c);
+ n = (n + 1) % m;
+ if (!n)
+ return 1;
+ } else {
+ n = 0;
+ kdb_printf("\n%s %s to enter the debugger.\n",
+ kgdb_fiq_knock ? "Type" : "Hit",
+ kgdb_fiq_knock ? magic : "<return>");
+ }
+ return 0;
+}
+
static unsigned int kgdb_fiq;
static void (*kgdb_enable_fiq)(unsigned int irq, bool on);
static bool (*is_kgdb_fiq)(unsigned int irq);
@@ -33,6 +79,8 @@ asmlinkage void __exception_irq_entry kgdb_fiq_do_handle(struct pt_regs *regs)
{
if (!is_kgdb_fiq(kgdb_fiq))
return;
+ if (!kgdb_fiq_poll_knock())
+ return;
nmi_enter();
kgdb_handle_exception(1, 0, 0, regs);
--
1.7.10.4
next prev parent reply other threads:[~2012-07-13 10:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 10:16 [PATCH v2 0/8] KGDB/KDB FIQ (NMI) debugger Anton Vorontsov
2012-07-13 10:16 ` [PATCH 1/8] kernel/debug: Make use of KGDB_REASON_NMI Anton Vorontsov
2012-07-13 10:16 ` [PATCH 2/8] kernel/debug: Mask KGDB NMI upon entry Anton Vorontsov
2012-07-13 10:16 ` [PATCH 3/8] ARM: Move some macros from entry-armv to entry-header Anton Vorontsov
2012-07-13 10:16 ` [PATCH 4/8] ARM: Add KGDB/KDB FIQ debugger generic code Anton Vorontsov
2012-07-13 10:16 ` Anton Vorontsov [this message]
2012-07-13 10:16 ` [PATCH 6/8] ARM: VIC: Add a couple of low-level FIQ management helpers Anton Vorontsov
2012-07-13 10:16 ` [PATCH 7/8] ARM: versatile: Make able to use UART ports for KGDB FIQ debugger Anton Vorontsov
2012-07-13 10:16 ` [PATCH 8/8] ARM: Get rid of .LCcralign local label usage in alignment_trap macro Anton Vorontsov
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=1342174608-22407-5-git-send-email-anton.vorontsov@linaro.org \
--to=anton.vorontsov@linaro.org \
--cc=arve@android.com \
--cc=ccross@android.com \
--cc=jason.wessel@windriver.com \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=patches@linaro.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).