aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorJason Wessel <jason.wessel@windriver.com>2010-10-25 11:14:05 -0400
committerJason Wessel <jason.wessel@windriver.com>2010-10-29 14:14:39 -0400
commit4aad8f51d0672f1c95e2cf0e1bc7b9ab42d8e1ea (patch)
tree51dc43c1b455cb6e166642051f64c80c7dd1d0b5
parent12ba8d1e9262ce81a695795410bd9ee5c9407ba1 (diff)
kdb: Add kdb kernel module sample
Add an example of how to add a dynamic kdb shell command via a kernel module. Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
-rw-r--r--Documentation/DocBook/kgdb.tmpl13
-rw-r--r--samples/Kconfig7
-rw-r--r--samples/Makefile2
-rw-r--r--samples/kdb/Makefile1
-rw-r--r--samples/kdb/kdb_hello.c60
5 files changed, 81 insertions, 2 deletions
diff --git a/Documentation/DocBook/kgdb.tmpl b/Documentation/DocBook/kgdb.tmpl
index 490d862c5f0d..d71b57fcf116 100644
--- a/Documentation/DocBook/kgdb.tmpl
+++ b/Documentation/DocBook/kgdb.tmpl
@@ -710,7 +710,18 @@ Task Addr Pid Parent [*] cpu State Thread Command
710 <listitem><para>A simple shell</para></listitem> 710 <listitem><para>A simple shell</para></listitem>
711 <listitem><para>The kdb core command set</para></listitem> 711 <listitem><para>The kdb core command set</para></listitem>
712 <listitem><para>A registration API to register additional kdb shell commands.</para> 712 <listitem><para>A registration API to register additional kdb shell commands.</para>
713 <para>A good example of a self-contained kdb module is the "ftdump" command for dumping the ftrace buffer. See: kernel/trace/trace_kdb.c</para></listitem> 713 <itemizedlist>
714 <listitem><para>A good example of a self-contained kdb module
715 is the "ftdump" command for dumping the ftrace buffer. See:
716 kernel/trace/trace_kdb.c</para></listitem>
717 <listitem><para>For an example of how to dynamically register
718 a new kdb command you can build the kdb_hello.ko kernel module
719 from samples/kdb/kdb_hello.c. To build this example you can
720 set CONFIG_SAMPLES=y and CONFIG_SAMPLE_KDB=m in your kernel
721 config. Later run "modprobe kdb_hello" and the next time you
722 enter the kdb shell, you can run the "hello"
723 command.</para></listitem>
724 </itemizedlist></listitem>
714 <listitem><para>The implementation for kdb_printf() which 725 <listitem><para>The implementation for kdb_printf() which
715 emits messages directly to I/O drivers, bypassing the kernel 726 emits messages directly to I/O drivers, bypassing the kernel
716 log.</para></listitem> 727 log.</para></listitem>
diff --git a/samples/Kconfig b/samples/Kconfig
index 954a1d550c5f..e03cf0e374d7 100644
--- a/samples/Kconfig
+++ b/samples/Kconfig
@@ -54,4 +54,11 @@ config SAMPLE_KFIFO
54 54
55 If in doubt, say "N" here. 55 If in doubt, say "N" here.
56 56
57config SAMPLE_KDB
58 tristate "Build kdb command exmaple -- loadable modules only"
59 depends on KGDB_KDB && m
60 help
61 Build an example of how to dynamically add the hello
62 command to the kdb shell.
63
57endif # SAMPLES 64endif # SAMPLES
diff --git a/samples/Makefile b/samples/Makefile
index 76b3c3455c29..f26c0959fd86 100644
--- a/samples/Makefile
+++ b/samples/Makefile
@@ -1,4 +1,4 @@
1# Makefile for Linux samples code 1# Makefile for Linux samples code
2 2
3obj-$(CONFIG_SAMPLES) += kobject/ kprobes/ tracepoints/ trace_events/ \ 3obj-$(CONFIG_SAMPLES) += kobject/ kprobes/ tracepoints/ trace_events/ \
4 hw_breakpoint/ kfifo/ 4 hw_breakpoint/ kfifo/ kdb/
diff --git a/samples/kdb/Makefile b/samples/kdb/Makefile
new file mode 100644
index 000000000000..fbedf39d9356
--- /dev/null
+++ b/samples/kdb/Makefile
@@ -0,0 +1 @@
obj-$(CONFIG_SAMPLE_KDB) += kdb_hello.o
diff --git a/samples/kdb/kdb_hello.c b/samples/kdb/kdb_hello.c
new file mode 100644
index 000000000000..c1c2fa0f62c2
--- /dev/null
+++ b/samples/kdb/kdb_hello.c
@@ -0,0 +1,60 @@
1/*
2 * Created by: Jason Wessel <jason.wessel@windriver.com>
3 *
4 * Copyright (c) 2010 Wind River Systems, Inc. All Rights Reserved.
5 *
6 * This file is licensed under the terms of the GNU General Public
7 * License version 2. This program is licensed "as is" without any
8 * warranty of any kind, whether express or implied.
9 */
10
11#include <linux/module.h>
12#include <linux/kdb.h>
13
14/*
15 * All kdb shell command call backs receive argc and argv, where
16 * argv[0] is the command the end user typed
17 */
18static int kdb_hello_cmd(int argc, const char **argv)
19{
20 if (argc > 1)
21 return KDB_ARGCOUNT;
22
23 if (argc)
24 kdb_printf("Hello %s.\n", argv[1]);
25 else
26 kdb_printf("Hello world!\n");
27
28 return 0;
29}
30
31
32static int __init kdb_hello_cmd_init(void)
33{
34 /*
35 * Registration of a dynamically added kdb command is done with
36 * kdb_register() with the arguments being:
37 * 1: The name of the shell command
38 * 2: The function that processes the command
39 * 3: Description of the usage of any arguments
40 * 4: Descriptive text when you run help
41 * 5: Number of characters to complete the command
42 * 0 == type the whole command
43 * 1 == match both "g" and "go" for example
44 */
45 kdb_register("hello", kdb_hello_cmd, "[string]",
46 "Say Hello World or Hello [string]", 0);
47 return 0;
48}
49
50static void __exit kdb_hello_cmd_exit(void)
51{
52 kdb_unregister("hello");
53}
54
55module_init(kdb_hello_cmd_init);
56module_exit(kdb_hello_cmd_exit);
57
58MODULE_AUTHOR("WindRiver");
59MODULE_DESCRIPTION("KDB example to add a hello command");
60MODULE_LICENSE("GPL");