| /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 …]
|
| H A D | index.rst | 20 aml-debugger
|
| /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 …]
|
| /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 …]
|
| H A D | dbinput.c | 4 * Module Name: dbinput - user front-end to the AML debugger
33 * Top-level debugger commands.
195 * Help for all debugger commands. First argument is the number of lines
199 * the debugger.
393 * DESCRIPTION: Display help information for a Debugger command.
418 * if not specified, all debugger command
423 * DESCRIPTION: Display help for a single debugger command, or all of them.
435 acpi_os_printf("\nSummary of AML Debugger Commands\n\n"); in acpi_db_display_help()
1207 * DESCRIPTION: Debugger execute thread. Waits for a command line, then
1227 * DESCRIPTION: Command line execution for the AML debugger. Commands are
|
| H A D | dbexec.c | 4 * Module Name: dbexec - debugger control method execution
153 /* Clear the abort and fall back to the debugger prompt */ in acpi_db_execute_method()
164 "while executing %s from AML Debugger", in acpi_db_execute_method()
169 "Possible buffer overflow within AML Debugger " in acpi_db_execute_method()
357 * Allow one execution to be performed by debugger or single step in acpi_db_execute()
361 acpi_os_printf("Only one debugger execution is allowed.\n"); in acpi_db_execute()
502 * DESCRIPTION: Debugger execute thread. Waits for a command line, then
593 ("Could not signal debugger thread sync semaphore, %s\n", in acpi_db_method_thread()
|
| H A D | dbtest.c | 70 * Support for the special debugger read/write control methods.
81 /* ASL Definitions of the debugger read/write control methods. AML below. */
176 /* Install the debugger read-object control method if necessary */ in acpi_db_test_all_objects()
182 ("%s, Could not install debugger read method\n", in acpi_db_test_all_objects()
197 /* Install the debugger write-object control method if necessary */ in acpi_db_test_all_objects()
203 ("%s, Could not install debugger write method\n", in acpi_db_test_all_objects()
621 char *value_to_write = "Test String from AML Debugger"; in acpi_db_test_string_type()
801 * special debugger control method that reads the object. Thus,
885 * special debugger control method that writes the object. Thus,
|
| H A D | dbfileio.c | 4 * Module Name: dbfileio - Debugger file I/O commands. These can't usually
5 * be used when running the debugger in Ring 0 (Kernel mode)
|
| /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 */
|
| /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
152 If an architecture can definitely handle entering the debugger
|
| /linux/include/uapi/linux/ |
| H A D | kfd_ioctl.h | 41 * - 1.13 - Add debugger API
1064 * wait for debugger process to send runtime exception EC_PROCESS_RUNTIME
1160 * @exception_mask (IN) - exceptions to raise to the debugger
1163 * @dbg_fd (IN) - fd the KFD will nofify the debugger with of raised
1211 * Set new exceptions to be raised to the debugger.
1213 * @exception_mask (IN) - new exceptions to raise the debugger
1283 * resumed. This allows the debugger to access queue information and
1458 * The debugger specifies the size of the array allocated in @num_queues.
1460 * larger than the size specified by the debugger, KFD will not overflow
1461 * the array allocated by the debugger.
[all …]
|
| /linux/arch/x86/include/asm/ |
| H A D | sighandling.h | 29 * handler if the trap flag (TF) is set without an external debugger attached,
41 * augmented SS, thus a debugger won't skip over the following instruction. in prevent_single_step_upon_eretu()
|
| /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; }
|
| /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
|
| /linux/kernel/debug/ |
| H A D | debug_core.h | 15 * debugger core and the debugger front end code.
|
| H A D | Makefile | 3 # Makefile for the linux kernel debugger
|
| /linux/Documentation/admin-guide/LSM/ |
| H A D | Yama.rst | 63 inferior can call ``prctl(PR_SET_PTRACER, debugger, ...)`` to declare
64 an allowed debugger PID to call ``PTRACE_ATTACH`` on the inferior.
|
| /linux/kernel/debug/kdb/ |
| H A D | kdb_private.h | 5 * Kernel Debugger Architecture Independent Private Headers
18 /* Kernel Debugger Command codes. Must not overlap with error codes. */
116 /* Routine for debugging the debugger state. */
|
| /linux/arch/x86/kvm/ |
| H A D | hyperv.h | 33 * The #defines related to the synthetic debugger are required by KDNet, but
34 * they are not documented in the Hyper-V TLFS because the synthetic debugger
43 * Hyper-V synthetic debugger platform capabilities
|
| /linux/arch/riscv/kernel/ |
| H A D | signal.c | 414 * debugger will see the already changed PC. in arch_do_signal_or_restart()
429 * the debugger may change all of our registers. in arch_do_signal_or_restart()
435 * debugger has chosen to restart at a different PC. in arch_do_signal_or_restart()
452 * Handle restarting a different system call. As above, if a debugger in arch_do_signal_or_restart()
|
| /linux/arch/powerpc/configs/ |
| H A D | hardening.config | 9 # Disable internal kernel debugger.
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-eud | 6 USB Debugger(EUD). This enables and disables the
|
| /linux/arch/x86/kernel/ |
| H A D | step.c | 99 * it, and a debugger could emulate this in is_setting_trap_flag()
210 * So no one should try to use debugger block stepping in a program in enable_step()
|
| /linux/Documentation/features/debug/kgdb/ |
| H A D | arch-support.txt | 4 # description: arch supports the kGDB kernel debugger
|