| /kernel/linux/linux-4.19/Documentation/s390/ |
| D | s390dbf.txt | 1 S390 Debug Feature
4 files: arch/s390/kernel/debug.c
5 arch/s390/include/asm/debug.h
9 The goal of this feature is to provide a kernel debug logging API
11 (e.g. device drivers) can have one separate debug log.
12 One purpose of this is to inspect the debug logs after a production system crash
15 it is possible to look at the debug logs on a live system via the Linux
17 The debug feature may also very useful for kernel and driver development.
21 Kernel components (e.g. device drivers) can register themselves at the debug
23 debug log for the caller. For each debug log exists a number of debug areas
[all …]
|
| /kernel/linux/linux-5.10/arch/s390/include/asm/ |
| D | debug.h | 3 * S/390 debug facility
17 #define DEBUG_MAX_LEVEL 6 /* debug levels range from 0 to 6 */
18 #define DEBUG_OFF_LEVEL -1 /* level where debug is switched off */
22 #define DEBUG_DEFAULT_LEVEL 3 /* initial debug level */
24 #define DEBUG_DIR_ROOT "s390dbf" /* name of debug root directory in proc fs */
29 #define __DEBUG_FEATURE_VERSION 3 /* version of debug feature */
105 /* Debug Feature API: */
123 * debug_level_enabled() - Returns true if debug events for the specified
126 * @id: handle for debug log
127 * @level: debug level
[all …]
|
| /kernel/linux/linux-5.10/Documentation/s390/ |
| D | s390dbf.rst | 2 S390 Debug Feature
6 - arch/s390/kernel/debug.c
7 - arch/s390/include/asm/debug.h
11 The goal of this feature is to provide a kernel debug logging API
13 (e.g. device drivers) can have one separate debug log.
14 One purpose of this is to inspect the debug logs after a production system crash
18 it is possible to look at the debug logs on a live system via the Linux
21 The debug feature may also very useful for kernel and driver development.
25 Kernel components (e.g. device drivers) can register themselves at the debug
28 debug log for the caller. For each debug log exists a number of debug areas
[all …]
|
| /kernel/linux/linux-4.19/Documentation/trace/ |
| D | coresight-cpu-debug.txt | 1 Coresight CPU Debug Module
10 Coresight CPU debug module is defined in ARMv8-a architecture reference manual
11 (ARM DDI 0487A.k) Chapter 'Part H: External debug', the CPU can integrate
12 debug module and it is mainly used for two modes: self-hosted debug and
13 external debug. Usually the external debug mode is well known as the external
15 explore debugging method which rely on self-hosted debug mode, this document
18 The debug module provides sample-based profiling extension, which can be used
20 every CPU has one dedicated debug module to be connected. Based on self-hosted
21 debug mechanism, Linux kernel can access these related registers from mmio
35 - At the time this documentation was written, the debug driver mainly relies on
[all …]
|
| /kernel/linux/linux-5.10/Documentation/trace/coresight/ |
| D | coresight-cpu-debug.rst | 2 Coresight CPU Debug Module
11 Coresight CPU debug module is defined in ARMv8-a architecture reference manual
12 (ARM DDI 0487A.k) Chapter 'Part H: External debug', the CPU can integrate
13 debug module and it is mainly used for two modes: self-hosted debug and
14 external debug. Usually the external debug mode is well known as the external
16 explore debugging method which rely on self-hosted debug mode, this document
19 The debug module provides sample-based profiling extension, which can be used
21 every CPU has one dedicated debug module to be connected. Based on self-hosted
22 debug mechanism, Linux kernel can access these related registers from mmio
36 - At the time this documentation was written, the debug driver mainly relies on
[all …]
|
| /kernel/linux/linux-5.10/arch/powerpc/kernel/ptrace/ |
| D | ptrace-adv.c | 13 task->thread.debug.dbcr0 &= ~DBCR0_BT; in user_enable_single_step()
14 task->thread.debug.dbcr0 |= DBCR0_IDM | DBCR0_IC; in user_enable_single_step()
25 task->thread.debug.dbcr0 &= ~DBCR0_IC; in user_enable_block_step()
26 task->thread.debug.dbcr0 = DBCR0_IDM | DBCR0_BT; in user_enable_block_step()
40 * And, after doing so, if all debug flags are off, turn in user_disable_single_step()
43 task->thread.debug.dbcr0 &= ~(DBCR0_IC | DBCR0_BT); in user_disable_single_step()
47 if (!DBCR_ACTIVE_EVENTS(task->thread.debug.dbcr0, in user_disable_single_step()
48 task->thread.debug.dbcr1)) { in user_disable_single_step()
50 * All debug events were off..... in user_disable_single_step()
52 task->thread.debug.dbcr0 &= ~DBCR0_IDM; in user_disable_single_step()
[all …]
|
| /kernel/linux/linux-5.10/tools/testing/selftests/kvm/x86_64/ |
| D | debug_regs.c | 3 * KVM guest debug register tests
17 /* For testing data access debug BP */
54 #define CLEAR_DEBUG() memset(&debug, 0, sizeof(debug))
55 #define APPLY_DEBUG() vcpu_set_guest_debug(vm, VCPU_ID, &debug)
66 struct kvm_guest_debug debug; in main() local
93 debug.control = KVM_GUESTDBG_ENABLE | KVM_GUESTDBG_USE_SW_BP; in main()
97 run->debug.arch.exception == BP_VECTOR && in main()
98 run->debug.arch.pc == CAST_TO_RIP(sw_bp), in main()
100 run->exit_reason, run->debug.arch.exception, in main()
101 run->debug.arch.pc, CAST_TO_RIP(sw_bp)); in main()
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/msm/dp/ |
| D | dp_debug.c | 49 struct dp_debug_private *debug = file->private_data; in dp_debug_read_info() local
57 if (!debug) in dp_debug_read_info()
67 drm_mode = &debug->panel->dp_mode.drm_mode; in dp_debug_read_info()
75 debug->panel->max_pclk_khz); in dp_debug_read_info()
81 debug->panel->link_info.rate); in dp_debug_read_info()
87 debug->panel->link_info.num_lanes); in dp_debug_read_info()
93 debug->panel->link_info.capabilities); in dp_debug_read_info()
127 debug->panel->dp_mode.h_active_low, in dp_debug_read_info()
128 debug->panel->dp_mode.v_active_low); in dp_debug_read_info()
152 debug->panel->dp_mode.bpp); in dp_debug_read_info()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/usb/ |
| D | usb3-debug-port.rst | 2 USB3 debug port
11 This is a HOWTO for using the USB3 debug port on x86 systems.
14 debug port, you need to::
16 1) check whether any USB3 debug port is available in
24 The xHCI debug capability (DbC) is an optional but standalone
28 When DbC is initialized and enabled, it will present a debug
29 device through the debug port (normally the first USB3
30 super-speed port). The debug device is fully compliant with
32 performance full-duplex serial link between the debug target
33 (the system under debugging) and a debug host.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/driver-api/usb/ |
| D | usb3-debug-port.rst | 2 USB3 debug port
11 This is a HOWTO for using the USB3 debug port on x86 systems.
14 debug port, you need to::
16 1) check whether any USB3 debug port is available in
24 The xHCI debug capability (DbC) is an optional but standalone
28 When DbC is initialized and enabled, it will present a debug
29 device through the debug port (normally the first USB3
30 super-speed port). The debug device is fully compliant with
32 performance full-duplex serial link between the debug target
33 (the system under debugging) and a debug host.
[all …]
|
| /kernel/linux/linux-5.10/include/linux/wimax/ |
| D | debug.h | 4 * Collection of tools to manage debug operations.
14 * debug action (like printing a message) if the current debug level
22 * A call to d_test(L) (L being the target debug level) returns true
23 * if the action should be taken because the current debug levels
30 * DEBUG LEVELS
34 * Convention sets 0 as "no debug" (so an action marked as debug level 0
35 * will always be taken). The increasing debug levels are used for
48 * - a debug-levels.h header file that declares the list of
52 * - some (optional) .c code to manipulate the runtime debug levels
55 * The debug-levels.h file would look like:
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/ |
| D | Kconfig.debug | 132 Say Y here if you want the debug print routines to direct
190 Say Y here if you want the debug print routines to direct
219 Say Y here if you want the debug print routines to direct
229 This low level debug works for Broadcom
238 bool "Marvell Berlin SoC Debug UART"
246 bool "Use BRCMSTB UART for low-level debug"
249 Say Y here if you want the debug print routines to direct
261 Say Y here if you want the debug print routines to direct
268 Say Y here if you want the debug print routines to direct
276 Say Y here if you want the debug print routines to direct
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | debugfs-hisi-hpre | 1 What: /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/regs
4 Description: Dump debug registers from the HPRE cluster.
7 What: /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/cluster_ctrl
11 and then we can read the debug information of the core.
14 What: /sys/kernel/debug/hisi_hpre/<bdf>/rdclr_en
17 Description: HPRE cores debug registers read clear control. 1 means enable
23 What: /sys/kernel/debug/hisi_hpre/<bdf>/current_qm
30 What: /sys/kernel/debug/hisi_hpre/<bdf>/regs
33 Description: Dump debug registers from the HPRE.
36 What: /sys/kernel/debug/hisi_hpre/<bdf>/qm/regs
[all …]
|
| D | debugfs-hisi-zip | 1 What: /sys/kernel/debug/hisi_zip/<bdf>/comp_core[01]/regs
4 Description: Dump of compression cores related debug registers.
7 What: /sys/kernel/debug/hisi_zip/<bdf>/decomp_core[0-5]/regs
10 Description: Dump of decompression cores related debug registers.
13 What: /sys/kernel/debug/hisi_zip/<bdf>/clear_enable
16 Description: Compression/decompression core debug registers read clear
22 What: /sys/kernel/debug/hisi_zip/<bdf>/current_qm
29 What: /sys/kernel/debug/hisi_zip/<bdf>/qm/regs
32 Description: Dump of QM related debug registers.
34 has one debug register.
[all …]
|
| D | debugfs-hisi-sec | 1 What: /sys/kernel/debug/hisi_sec2/<bdf>/clear_enable
5 the SEC debug registers.
9 What: /sys/kernel/debug/hisi_sec2/<bdf>/current_qm
17 What: /sys/kernel/debug/hisi_sec2/<bdf>/qm/qm_regs
20 Description: Dump of QM related debug registers.
22 has one debug register.
24 What: /sys/kernel/debug/hisi_sec2/<bdf>/qm/current_q
28 queue to show its debug registers in above 'regs'.
31 What: /sys/kernel/debug/hisi_sec2/<bdf>/qm/clear_enable
35 the SEC's QM debug registers.
[all …]
|
| /kernel/linux/linux-4.19/Documentation/wimax/ |
| D | README.i2400m | 149 5.2. Debug operations: debugfs entries
152 debug settings. There are three main container directories where
155 * /sys/kernel/debug/wimax:DEVNAME/ for the generic WiMAX stack
157 * /sys/kernel/debug/wimax:DEVNAME/i2400m for the i2400m generic
159 * /sys/kernel/debug/wimax:DEVNAME/i2400m-usb (or -sdio) for the
163 /sys/kernel/debug, those paths will change.
165 5.2.1. Increasing debug output
167 The files named *dl_* indicate knobs for controlling the debug output
170 # find /sys/kernel/debug/wimax\:wmx0 -name \*dl_\*
171 /sys/kernel/debug/wimax:wmx0/i2400m-usb/dl_tx
[all …]
|
| D | README.wimax | 39 files will appear in /sys/kernel/debug/wimax:wmxX can tweak for
42 2.1. Obtaining debug information: debugfs entries
44 The WiMAX stack is compiled, by default, with debug messages that can
48 debug settings.
54 2.1.1. Increasing debug output
56 The files named *dl_* indicate knobs for controlling the debug output
59 # find /sys/kernel/debug/wimax\:wmx0 -name \*dl_\*
60 /sys/kernel/debug/wimax:wmx0/wimax_dl_stack
61 /sys/kernel/debug/wimax:wmx0/wimax_dl_op_rfkill
62 /sys/kernel/debug/wimax:wmx0/wimax_dl_op_reset
[all …]
|
| /kernel/linux/linux-4.19/include/linux/wimax/ |
| D | debug.h | 3 * Collection of tools to manage debug operations.
30 * debug action (like printing a message) if the current debug level
38 * A call to d_test(L) (L being the target debug level) returns true
39 * if the action should be taken because the current debug levels
47 * DEBUG LEVELS
51 * Convention sets 0 as "no debug" (so an action marked as debug level 0
52 * will always be taken). The increasing debug levels are used for
67 * - a debug-levels.h header file that declares the list of
71 * - some (optional) .c code to manipulate the runtime debug levels
74 * The debug-levels.h file would look like:
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/arm/ |
| D | coresight-cpu-debug.txt | 1 * CoreSight CPU Debug Component:
3 CoreSight CPU debug component are compliant with the ARMv8 architecture
4 reference manual (ARM DDI 0487A.k) Chapter 'Part H: External debug'. The
5 external debug module is mainly used for two modes: self-hosted debug and
6 external debug, and it can be accessed from mmio region from Coresight
7 and eventually the debug module connects with CPU for debugging. And the
8 debug module provides sample-based profiling extension, which can be used
10 usually every CPU has one dedicated debug module to be connected.
14 - compatible : should be "arm,coresight-cpu-debug"; supplemented with
25 mandatory. The interface between the debug logic and the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/ |
| D | coresight-cpu-debug.txt | 1 * CoreSight CPU Debug Component:
3 CoreSight CPU debug component are compliant with the ARMv8 architecture
4 reference manual (ARM DDI 0487A.k) Chapter 'Part H: External debug'. The
5 external debug module is mainly used for two modes: self-hosted debug and
6 external debug, and it can be accessed from mmio region from Coresight
7 and eventually the debug module connects with CPU for debugging. And the
8 debug module provides sample-based profiling extension, which can be used
10 usually every CPU has one dedicated debug module to be connected.
14 - compatible : should be "arm,coresight-cpu-debug"; supplemented with
25 mandatory. The interface between the debug logic and the
[all …]
|
| /kernel/linux/linux-4.19/arch/arm/ |
| D | Kconfig.debug | 125 Say Y here if you want the debug print routines to direct
183 Say Y here if you want the debug print routines to direct
212 Say Y here if you want the debug print routines to direct
222 This low level debug works for Broadcom
231 bool "Marvell Berlin SoC Debug UART"
239 bool "Use BRCMSTB UART for low-level debug"
242 Say Y here if you want the debug print routines to direct
254 Say Y here if you want the debug print routines to direct
261 Say Y here if you want the debug print routines to direct
269 Say Y here if you want the debug print routines to direct
[all …]
|
| /kernel/linux/linux-4.19/Documentation/fault-injection/ |
| D | fault-injection.txt | 31 debugfs entries under /sys/kernel/debug/mmc0/fail_mmc_request
37 under /sys/kernel/debug/fail_function. No boot option supported.
42 debugfs entries under /sys/kernel/debug/nvme*/fault_inject. The default
55 - /sys/kernel/debug/fail*/probability:
62 /sys/kernel/debug/fail*/interval for such testcases.
64 - /sys/kernel/debug/fail*/interval:
72 - /sys/kernel/debug/fail*/times:
77 - /sys/kernel/debug/fail*/space:
83 - /sys/kernel/debug/fail*/verbose
89 to debug the problems revealed by fault injection.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/fault-injection/ |
| D | fault-injection.rst | 36 debugfs entries under /sys/kernel/debug/mmc0/fail_mmc_request
42 under /sys/kernel/debug/fail_function. No boot option supported.
47 debugfs entries under /sys/kernel/debug/nvme*/fault_inject. The default
61 - /sys/kernel/debug/fail*/probability:
69 /sys/kernel/debug/fail*/interval for such testcases.
71 - /sys/kernel/debug/fail*/interval:
79 - /sys/kernel/debug/fail*/times:
84 - /sys/kernel/debug/fail*/space:
90 - /sys/kernel/debug/fail*/verbose
97 to debug the problems revealed by fault injection.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/wimax/ |
| D | wimax.rst | 44 files will appear in /sys/kernel/debug/wimax:wmxX can tweak for
47 2.1. Obtaining debug information: debugfs entries
50 The WiMAX stack is compiled, by default, with debug messages that can
54 debug settings.
60 2.1.1. Increasing debug output
63 The files named *dl_* indicate knobs for controlling the debug output
66 # find /sys/kernel/debug/wimax\:wmx0 -name \*dl_\*
67 /sys/kernel/debug/wimax:wmx0/wimax_dl_stack
68 /sys/kernel/debug/wimax:wmx0/wimax_dl_op_rfkill
69 /sys/kernel/debug/wimax:wmx0/wimax_dl_op_reset
[all …]
|
| D | i2400m.rst | 162 5.2. Debug operations: debugfs entries
166 debug settings. There are three main container directories where
170 * /sys/kernel/debug/wimax:DEVNAME/ for the generic WiMAX stack
172 * /sys/kernel/debug/wimax:DEVNAME/i2400m for the i2400m generic
174 * /sys/kernel/debug/wimax:DEVNAME/i2400m-usb (or -sdio) for the
178 /sys/kernel/debug, those paths will change.
180 5.2.1. Increasing debug output
183 The files named *dl_* indicate knobs for controlling the debug output
186 # find /sys/kernel/debug/wimax\:wmx0 -name \*dl_\*
187 /sys/kernel/debug/wimax:wmx0/i2400m-usb/dl_tx
[all …]
|