| /openbmc/linux/Documentation/firmware-guide/acpi/ |
| H A D | aml-debugger.rst | 5 The AML Debugger
12 This document describes the usage of the AML debugger embedded in the Linux
15 1. Build the debugger
19 debugger interface from the Linux kernel::
37 2. Start the userspace debugger interface
40 After booting the kernel with the debugger built-in, the debugger can be
47 That spawns the interactive AML debugger environment where you can execute
48 debugger commands.
55 The detailed debugger commands reference is located in Chapter 12 "ACPICA
56 Debugger Reference". The "help" command can be used for a quick reference.
[all …]
|
| /openbmc/linux/drivers/acpi/ |
| H A D | acpi_dbg.c | 75 * The debugger interface is in opened state (OPENED && !CLOSED), in __acpi_aml_access_ok()
76 * then it is allowed to access the debugger buffers from either in __acpi_aml_access_ok()
78 * In addition, for the kernel space, only the debugger thread in __acpi_aml_access_ok()
151 * starts and the stops of the debugger thread. in acpi_aml_used()
293 * acpi_aml_write_log() - Capture debugger output
294 * @msg: the debugger output
297 * the debugger output and store the output into the debugger interface
332 * acpi_aml_read_cmd() - Capture debugger input
333 * @msg: the debugger input
334 * @size: the size of the debugger input
[all …]
|
| /openbmc/linux/Documentation/dev-tools/ |
| H A D | kgdb.rst | 2 Using kgdb, kdb and the kernel debugger internals
10 The kernel has two different debugger front ends (kdb and kgdb) which
12 debugger front ends and dynamically transition between them if you
18 stop in a certain location. Kdb is not a source level debugger, although
25 Kgdb is intended to be used as a source level debugger for the Linux
56 :menuselection:`KGDB: kernel debugger`.
67 or on the stack at different points which allows a debugger such as gdb to
123 Kernel Debugger Boot Arguments
127 the configuration of the kernel debugger. The following chapter covers
150 that has atomic mode setting hooks, it is possible to enter the debugger
[all …]
|
| /openbmc/linux/arch/sparc/include/asm/ |
| H A D | kdebug_32.h | 15 * if you want to drop into the debugger you do:
30 /* First the entry point into the debugger. You jump here
31 * to give control over to the debugger.
35 /* The following is the number of pages that the debugger has
41 * this synchronization function so the debugger can check out
49 /* Use this macro in C-code to enter the debugger. */
|
| /openbmc/linux/drivers/acpi/acpica/ |
| H A D | acdebug.h | 4 * Name: acdebug.h - ACPI/AML debugger
13 /* The debugger is used in conjunction with the disassembler most of time */
50 * dbxface - external debugger interfaces
193 * dbexec - debugger control method execution
213 * dbfileio - Debugger file I/O commands
228 * dbhistry - debugger HISTORY command
239 * dbinput - user front-end to the AML debugger
278 * dbutils - AML debugger utilities
|
| H A D | dbxface.c | 4 * Module Name: dbxface - AML Debugger external interfaces
43 * DESCRIPTION: Enter debugger command loop
115 * Set the single-step flag. This will cause the debugger (if present) in acpi_db_signal_break_point()
116 * to break to the console within the AML debugger at the start of the in acpi_db_signal_break_point()
391 * DESCRIPTION: Init and start debugger
441 acpi_os_printf("Could not get debugger mutex\n"); in acpi_initialize_debugger()
452 "Could not start debugger thread")); in acpi_initialize_debugger()
473 * DESCRIPTION: Stop debugger in ACPI_EXPORT_SYMBOL()
479 /* Terminate the AML Debugger */ in ACPI_EXPORT_SYMBOL()
485 /* Wait the AML Debugger threads */ in ACPI_EXPORT_SYMBOL()
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.bedbug | 4 These changes implement the bedbug (emBEDded deBUGger) debugger in U-Boot.
19 Added call to initialize debugger on startup.
55 AMCC PPC405 specific debugger routines.
64 Added call to initialize 860 debugger.
|
| /openbmc/linux/drivers/tty/serial/ |
| H A D | kgdb_nmi.c | 33 "must be used to enter the debugger; when set to 0, " \
34 "hitting return key is enough to enter the debugger; " \
35 "when set to -1, the debugger is entered immediately " \
40 MODULE_PARM_DESC(magic, "magic sequence to enter NMI debugger (default $3#33)");
148 kdb_printf("\r%s %s to enter the debugger> %*s", in kgdb_nmi_poll_one_knock()
157 * kgdb_nmi_poll_knock - Check if it is time to enter the debugger
165 * enter the debugger until we receive a known magic phrase (which is actually
168 * debugger. And if knocking is disabled, the function always returns 1.
|
| /openbmc/linux/arch/powerpc/ |
| H A D | Kconfig.debug | 94 bool "Include xmon kernel debugger"
98 Include in-kernel hooks for the xmon kernel monitor/debugger.
105 debugger hooks. 'xmon=off' will disable the debugger hooks
134 config DEBUGGER config
143 Include in-kernel support for the Abatron BDI2000 debugger.
284 kernel BSS and should be safe to select on any system. A debugger
|
| /openbmc/u-boot/board/synopsys/emsdp/ |
| H A D | README | 26 debugger on development host. Both proprietary MetaWare debugger and
57 2. To build Elf file (for example to be used with host debugger via JTAG
77 in "ROM" and start it from the debugger. One important note here we first
80 2.1. In case of proprietary MetaWare debugger run:
|
| /openbmc/linux/arch/x86/include/uapi/asm/ |
| H A D | vm86.h | 44 #define VM86_TRAP 6 /* return due to DOS-debugger request */
113 unsigned long vm86dbg_active:1; /* for debugger */
114 unsigned long vm86dbg_TFpendig:1; /* for debugger */
117 unsigned char vm86dbg_intxxtab[32]; /* for debugger */
|
| /openbmc/qemu/linux-user/i386/ |
| H A D | target_syscall.h | 63 #define TARGET_VM86_TRAP 6 /* return due to DOS-debugger request */
133 #define TARGET_vm86dbg_active (1 << 1) /* for debugger */
134 #define TARGET_vm86dbg_TFpendig (1 << 2) /* for debugger */
136 unsigned char vm86dbg_intxxtab[32]; /* for debugger */
|
| /openbmc/linux/kernel/debug/ |
| H A D | debug_core.c | 464 kdb_printf("ERROR: Task on cpu %d didn't stop in the debugger\n", in kdb_dump_stack_on_cpu()
488 * debugger is attached a message can be printed to the console about
489 * waiting for the debugger to attach.
493 * debugger to attach.
508 pr_crit("Waiting for remote debugger\n"); in kgdb_io_ready()
522 /* Panic on recursive debugger calls: */ in kgdb_reenter_check()
548 panic("Recursive entry to debugger"); in kgdb_reenter_check()
557 panic("Recursive entry to debugger"); in kgdb_reenter_check()
697 * CPU in a spin state while the debugger is active in kgdb_cpu_enter()
725 * in the debugger and all secondary CPUs are quiescent in kgdb_cpu_enter()
[all …]
|
| H A D | debug_core.h | 15 * debugger core and the debugger front end code.
|
| /openbmc/qemu/bsd-user/i386/ |
| H A D | target_syscall.h | 80 #define TARGET_VM86_TRAP 6 /* return due to DOS-debugger request */
150 #define TARGET_vm86dbg_active (1 << 1) /* for debugger */
151 #define TARGET_vm86dbg_TFpendig (1 << 2) /* for debugger */
153 unsigned char vm86dbg_intxxtab[32]; /* for debugger */
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-connectivity/freeradius/files/ |
| H A D | 0005-configure.ac-add-option-for-libcap.patch | 27 +[ --with-licap use licap for debugger checks. (default=yes)],
48 - AC_MSG_WARN([cap library not found, debugger checks will not be enabled. Use --with-cap-lib-dir=…
58 + AC_MSG_WARN([cap library not found, debugger checks will not be enabled. Use --with-cap-lib-di…
|
| /openbmc/linux/lib/ |
| H A D | Kconfig.kgdb | 12 bool "KGDB: kernel debugger"
20 backtraces in the external debugger. Documentation of
21 kernel debugger is available at http://kgdb.sourceforge.net
151 If an architecture can definitely handle entering the debugger
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-devtools/geany/ |
| H A D | geany-plugins_1.38.bb | 68 # | checking whether the GTK version in use is compatible with plugin Debugger... no
69 EXTRA_OECONF += "--disable-debugger"
70 #PLUGINS += "${PN}-debugger"
71 #LIC_FILES_CHKSUM += "file://debugger/COPYING;md5=4325afd396febcb659c36b49533135d4"
72 #FILES:${PN}-debugger = "${libdir}/geany/debugger.so ${datadir}/${PN}/debugger"
|
| /openbmc/u-boot/board/synopsys/hsdk/ |
| H A D | README | 26 debugger on development host. Both proprietary MetaWare debugger and
68 2. To build Elf file (for example to be used with host debugger via JTAG
101 in DDR and start it from the debugger.
103 2.1. In case of proprietary MetaWare debugger run:
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | kfd_ioctl.h | 41 * - 1.13 - Add debugger API
967 * wait for debugger process to send runtime exception EC_PROCESS_RUNTIME
1063 * @exception_mask (IN) - exceptions to raise to the debugger
1066 * @dbg_fd (IN) - fd the KFD will nofify the debugger with of raised
1114 * Set new exceptions to be raised to the debugger.
1116 * @exception_mask (IN) - new exceptions to raise the debugger
1186 * resumed. This allows the debugger to access queue information and
1361 * The debugger specifies the size of the array allocated in @num_queues.
1363 * larger than the size specified by the debugger, KFD will not overflow
1364 * the array allocated by the debugger.
[all …]
|
| /openbmc/linux/include/linux/ |
| H A D | kdb.h | 5 * Kernel Debugger Architecture Independent Global Headers
90 * number whenever the kernel debugger is entered.
151 * External entry point for the kernel debugger. The pt_regs
153 * entry to the kernel debugger.
|
| /openbmc/linux/Documentation/devicetree/bindings/soc/qcom/ |
| H A D | qcom,eud.yaml | 7 title: Qualcomm Embedded USB Debugger
13 This binding is used to describe the Qualcomm Embedded USB Debugger, which is
|
| /openbmc/linux/arch/powerpc/include/asm/ |
| H A D | debug.h | 30 DEBUGGER_BOILERPLATE(debugger)
39 static inline int debugger(struct pt_regs *regs) { return 0; }
|
| /openbmc/u-boot/board/synopsys/iot_devkit/ |
| H A D | README | 32 debugger on development host. Both proprietary MetaWare debugger and
80 2. To build Elf file (for example to be used with host debugger via JTAG
109 2.1. In case of proprietary MetaWare debugger run:
|
| /openbmc/linux/arch/x86/kvm/ |
| H A D | hyperv.h | 31 * The #defines related to the synthetic debugger are required by KDNet, but
32 * they are not documented in the Hyper-V TLFS because the synthetic debugger
41 * Hyper-V synthetic debugger platform capabilities
|