diff options
author | Jason Wessel <jason.wessel@windriver.com> | 2010-10-25 15:14:05 (GMT) |
---|---|---|
committer | Jason Wessel <jason.wessel@windriver.com> | 2010-10-29 18:14:39 (GMT) |
commit | 4aad8f51d0672f1c95e2cf0e1bc7b9ab42d8e1ea (patch) | |
tree | 51dc43c1b455cb6e166642051f64c80c7dd1d0b5 /Documentation | |
parent | 12ba8d1e9262ce81a695795410bd9ee5c9407ba1 (diff) | |
download | linux-fsl-qoriq-4aad8f51d0672f1c95e2cf0e1bc7b9ab42d8e1ea.tar.xz |
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>
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/DocBook/kgdb.tmpl | 13 |
1 files changed, 12 insertions, 1 deletions
diff --git a/Documentation/DocBook/kgdb.tmpl b/Documentation/DocBook/kgdb.tmpl index 490d862..d71b57f 100644 --- a/Documentation/DocBook/kgdb.tmpl +++ b/Documentation/DocBook/kgdb.tmpl @@ -710,7 +710,18 @@ Task Addr Pid Parent [*] cpu State Thread Command <listitem><para>A simple shell</para></listitem> <listitem><para>The kdb core command set</para></listitem> <listitem><para>A registration API to register additional kdb shell commands.</para> - <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> + <itemizedlist> + <listitem><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> + <listitem><para>For an example of how to dynamically register + a new kdb command you can build the kdb_hello.ko kernel module + from samples/kdb/kdb_hello.c. To build this example you can + set CONFIG_SAMPLES=y and CONFIG_SAMPLE_KDB=m in your kernel + config. Later run "modprobe kdb_hello" and the next time you + enter the kdb shell, you can run the "hello" + command.</para></listitem> + </itemizedlist></listitem> <listitem><para>The implementation for kdb_printf() which emits messages directly to I/O drivers, bypassing the kernel log.</para></listitem> |