Lines Matching +full:cm +full:- +full:poll +full:- +full:mode
15 Kdb is simplistic shell-style interface which you can use on a system
22 kernel built-ins or in kernel modules if the code was built with
40 kgdb I/O modules compiled as built-ins or loadable kernel modules in the
46 - In order to enable compilation of kdb, you must first enable kgdb.
48 - The kgdb test compile options are described in the kgdb test suite
52 ------------------------------
55 :menuselection:`Kernel hacking --> Kernel debugging` and select
73 certain regions of the kernel's memory space as read-only. If kgdb
93 -----------------------------
108 If you want to use a PS/2-style keyboard with kdb, you would select
132 ------------------------
144 built-in or a kernel loadable module. You can only make use of
146 a built-in.
148 Optionally you can elect to activate kms (Kernel Mode Setting)
150 that has atomic mode setting hooks, it is possible to enter the debugger
152 previous graphics mode will be restored. This integration can serve as a
168 - kms = Kernel Mode Setting
170 - kbd = Keyboard
178 Using loadable module or built-in
181 1. As a kernel built-in:
185 kgdboc=<tty-device>,[baud]
191 modprobe kgdboc kgdboc=<tty-device>,[baud]
247 4. kdb with kernel mode setting::
251 5. kdb with kernel mode setting and kgdb over a serial port::
258 protocol. You must manually send a :kbd:`SysRq-G` unless you have a proxy
261 "human" console. The proxy can take care of sending the :kbd:`SysRq-G`
272 don't like this are to hack gdb to send the :kbd:`SysRq-G` for you as well as
277 -------------------------------------
301 ------------------------------
316 -----------------------------
351 ----------------------------------
357 .. tabularcolumns:: |p{0.4cm}|p{11.5cm}|p{5.6cm}|
359 .. flat-table::
362 * - 1
363 - ``echo -1 > /sys/module/debug_core/parameters/kgdbreboot``
364 - Ignore the reboot notification entirely.
366 * - 2
367 - ``echo 0 > /sys/module/debug_core/parameters/kgdbreboot``
368 - Send the detach message to any attached debugger client.
370 * - 3
371 - ``echo 1 > /sys/module/debug_core/parameters/kgdbreboot``
372 - Enter the debugger on reboot notify.
375 -----------------------------
387 ------------------------------------
404 manually; all involve using the :kbd:`SysRq-G`, which means you must have
407 - When logged in as root or with a super user session you can run::
409 echo g > /proc/sysrq-trigger
411 - Example using minicom 2.2
413 Press: :kbd:`CTRL-A` :kbd:`f` :kbd:`g`
415 - When you have telneted to a terminal server that supports sending
418 Press: :kbd:`CTRL-]`
447 ------------------------------------------------------
463 manually; all involve using the :kbd:`SysRq-G`, which means you must have
466 - When logged in as root or with a super user session you can run::
468 echo g > /proc/sysrq-trigger
470 - Example using a laptop keyboard:
484 - Example using a PS/2 101-key keyboard
516 ------------------------------------
534 using kgdbwait as a boot argument, via a :kbd:`SysRq-G`, or running the
538 - When logged in as root or with a super user session you can run::
540 echo g > /proc/sysrq-trigger
542 - Example using minicom 2.2
544 Press: :kbd:`CTRL-A` :kbd:`f` :kbd:`g`
546 - When you have telneted to a terminal server that supports sending
549 Press: :kbd:`CTRL-]`
581 to issue an other :kbd:`SysRq-G`. It is easy to create a simple entry point by
590 in the same mode.
593 ------------------------------
600 Whenever the kernel debugger stops in kgdb mode it will print the
615 Now you must kill gdb. Typically you press :kbd:`CTRL-Z` and issue
618 kill -9 %
624 enter kgdb mode by issuing the kgdb command from the kdb shell prompt,
628 automatically changes into kgdb mode.
640 -----------------------------
688 ----------------------
697 - A generic OS exception handler which includes sync'ing the
698 processors into a stopped state on an multi-CPU system.
700 - The API to talk to the kgdb I/O drivers
702 - The API to make calls to the arch-specific kgdb implementation
704 - The logic to perform safe memory reads and writes to memory while
707 - A full implementation for software breakpoints unless overridden
710 - The API to invoke either the kdb or kgdb frontend to the debug
713 - The structures and callback API for atomic kernel mode setting.
717 2. kgdb arch-specific implementation
723 The arch-specific portion implements:
725 - contains an arch-specific trap catcher which invokes
728 - translation to and from gdb specific packet format to struct pt_regs
730 - Registration and unregistration of architecture specific trap
733 - Any special exception handling and cleanup
735 - NMI exception handling and cleanup
737 - (optional) HW breakpoints
743 - All the logic to implement the gdb serial protocol
754 - A simple shell
756 - The kdb core command set
758 - A registration API to register additional kdb shell commands.
760 - A good example of a self-contained kdb module is the ``ftdump``
764 - For an example of how to dynamically register a new kdb command
771 - The implementation for kdb_printf() which emits messages directly
774 - SW / HW breakpoint management for the kdb shell
781 - configuration via built-in or module
783 - dynamic configuration and kgdb hook registration calls
785 - read and write character interface
787 - A cleanup handler for unconfiguring from the kgdb core
789 - (optional) Early debug methodology
794 restoring them. The kgdb core will repeatedly "poll" a kgdb I/O
809 - ``NUMREGBYTES``:
813 - ``BUFMAX``:
817 - ``CACHE_FLUSH_IS_SAFE``:
824 ``kernel/kgdb.c``, that must be supplied by the architecture-specific
829 .. kernel-doc:: include/linux/kgdb.h
833 ----------------
842 doing polled mode reading and writing of a single character while in an
877 :c:expr:`kdb_poll_funcs[]`. The kdb_get_kbd_char() is the top-level
886 kernel mode setting support.
935 - Jason Wessel <jason.wessel@windriver.com>
939 - Jason Wessel <jason.wessel@windriver.com>