| /linux-6.15/arch/arm/ |
| H A D | Kconfig.debug | 125 prompt "Kernel low-level debugging port"
137 bool "Kernel low-level debugging via asm9260 UART"
178 bool "Kernel low-level debugging on SAMA5D2 UART1"
186 bool "Kernel low-level debugging on SAMA5D4 USART3"
194 bool "Kernel low-level debugging via SAMV7 USART1"
246 bool "Kernel low-level debugging on BCMBCA UART0"
274 bool "Kernel low-level debugging on BCM63XX UART"
691 bool "Kernel low-level debugging via OMAP1 UART1"
699 bool "Kernel low-level debugging via OMAP1 UART2"
707 bool "Kernel low-level debugging via OMAP1 UART3"
[all …]
|
| /linux-6.15/net/mac80211/ |
| H A D | Kconfig | 111 bool "Select mac80211 debugging features"
133 bool "Verbose debugging output"
155 bool "Verbose station debugging"
164 bool "Verbose HT debugging"
176 bool "Verbose OCB debugging"
187 bool "Verbose IBSS debugging"
198 bool "Verbose powersave mode debugging"
210 bool "Verbose mesh peer link debugging"
223 bool "Verbose mesh path debugging"
271 bool "Verbose mesh powersave debugging"
[all …]
|
| /linux-6.15/drivers/gpu/drm/xe/ |
| H A D | Kconfig.debug | 20 bool "Enable additional driver debugging"
26 Choose this option to turn on extra driver debugging that may affect
34 bool "Enable extra VM debugging info"
37 Enable extra VM debugging info
44 bool "Enable extra memirq debugging"
47 Choose this option to enable additional debugging info for
55 bool "Enable extra SR-IOV debugging"
59 Enable extra SR-IOV debugging info.
93 Choose this option when debugging guc issues.
104 Choose this option when debugging error paths that
|
| /linux-6.15/Documentation/process/debugging/ |
| H A D | index.rst | 14 gdb-kernel-debugging
35 General debugging advice
50 In this case your debugging capability depends on built-in debugging support of
52 The :doc:`/process/debugging/userspace_debugging_guide` provides a brief
53 overview over a range of possible debugging tools in that situation. You can
64 tools in the :doc:`/process/debugging/driver_development_debugging_guide`.
76 printk() for debugging purposes may not work, a similar alternative is to use
|
| H A D | media_specific_debugging_guide.rst | 7 This document serves as a starting point and lookup for debugging device
13 General debugging advice
17 </process/debugging/index>`.
37 debugging`
47 :ref:`process/debugging/driver_development_debugging_guide:printk() & friends`
64 :ref:`process/debugging/userspace_debugging_guide:dynamic debug` guide.
80 calls, etc. Very useful for debugging problems without changing the kernel and
84 :ref:`process/debugging/userspace_debugging_guide:ftrace` guide.
93 :ref:`process/debugging/driver_development_debugging_guide:debugfs` guide.
101 :ref:`process/debugging/userspace_debugging_guide:perf & alternatives` guide.
[all …]
|
| H A D | driver_development_debugging_guide.rst | 7 This document serves as a general starting point and lookup for debugging
9 While this guide focuses on debugging that requires re-compiling the
10 module/kernel, the :doc:`userspace debugging guide
11 </process/debugging/userspace_debugging_guide>` will guide
13 debugging issues and behavior.
14 For general debugging advice, see the :doc:`general advice document
15 </process/debugging/index>`.
71 :ref:`process/debugging/userspace_debugging_guide:dynamic debug` that contains
110 flow during a debugging session.
124 DebugFS differs from the other approaches of debugging, as it doesn't write
|
| /linux-6.15/net/dccp/ccids/ |
| H A D | Kconfig | 5 bool "CCID-2 debugging messages"
7 Enable CCID-2 specific debugging messages.
9 The debugging output can additionally be toggled by setting the
40 bool "CCID-3 debugging messages"
43 Enable CCID-3 specific debugging messages.
45 The debugging output can additionally be toggled by setting the
|
| /linux-6.15/fs/jbd2/ |
| H A D | Kconfig | 21 bool "JBD2 (ext4) debugging support"
26 allows you to enable debugging output while the system is running,
28 By default, the debugging output will be turned off.
30 If you select Y here, then you will be able to turn on debugging
32 number between 1 and 5. The higher the number, the more debugging
33 output is generated. To turn debugging off again, do
|
| /linux-6.15/arch/powerpc/ |
| H A D | Kconfig.debug | 169 bool "Early debugging (dangerous)"
179 prompt "Early debugging console"
182 Use the selected console for early debugging. Careful, if you
183 enable debugging for the wrong type of machine your kernel
211 Select this to enable early debugging for Apple G5 machines.
217 Select this to enable early debugging via the RTAS panel.
223 Select this to enable early debugging for PA Semi.
227 bool "Early serial debugging for IBM/AMCC 44x CPUs"
238 Select this to enable early debugging for Freescale chips
243 bool "Early debugging through the USB Gecko adapter"
[all …]
|
| /linux-6.15/drivers/infiniband/ulp/ipoib/ |
| H A D | Kconfig | 28 bool "IP-over-InfiniBand debugging" if EXPERT
32 This option causes debugging code to be compiled into the
38 debugfs, which contains files that expose debugging
43 bool "IP-over-InfiniBand data path debugging"
46 This option compiles debugging code into the data path
49 turned off, this debugging code will have some performance
|
| /linux-6.15/Documentation/power/ |
| H A D | drivers-testing.rst | 21 testing the new driver. Please see Documentation/power/basic-pm-debugging.rst
22 for more information about the debugging of suspend/resume functionality.
31 (see: Documentation/power/basic-pm-debugging.rst, 1).
34 "platform" modes (see: Documentation/power/basic-pm-debugging.rst, 1).
43 Documentation/power/basic-pm-debugging.rst, 2). [As far as the STR tests are
48 (see: Documentation/power/basic-pm-debugging.rst, 2).
|
| /linux-6.15/Documentation/driver-api/usb/ |
| H A D | usb3-debug-port.rst | 13 Before using any kernel debugging functionality based on USB3
18 2) check which port is used for debugging purposes;
19 3) have a USB 3.0 super-speed A-to-A debugging cable.
33 (the system under debugging) and a debug host.
39 this feature is kernel debugging. For example, when your machine
44 On the debug target system, you need to customize a debugging
63 should be a USB 3.0 super-speed A-to-A debugging cable.
126 speed A-to-A debugging cable. You can see /dev/ttyDBC0 created
151 The debug device works now. You can use any communication or debugging
|
| /linux-6.15/drivers/gpu/drm/i915/ |
| H A D | Kconfig.debug | 37 bool "Enable additional driver debugging"
66 Choose this option to turn on extra driver debugging that may affect
131 Enable additional and verbose debugging output that will spam
132 ordinary tests, but may be vital for post-mortem debugging when
145 Enable additional and verbose debugging output that will spam
146 ordinary tests, but may be vital for post-mortem debugging when
154 bool "Enable additional driver debugging for fence objects"
159 Choose this option to turn on extra driver debugging that may affect
171 Choose this option to turn on extra driver debugging that may affect
179 bool "Enable additional driver debugging for GuC"
[all …]
|
| /linux-6.15/fs/netfs/ |
| H A D | Kconfig | 23 debugging purposes. Saying 'Y' here is recommended.
26 bool "Enable dynamic debugging netfslib and FS-Cache"
29 This permits debugging to be dynamically enabled in the local caching
30 management module. If this is set, the debugging output may be
58 debugging purposes. Saying 'Y' here is recommended.
|
| /linux-6.15/kernel/debug/kdb/ |
| H A D | kdb_cmds | 7 # Standard debugging information for first level support, just type archkdb
10 defcmd dumpcommon "" "Common kdb debugging"
20 defcmd dumpall "" "First line debugging"
|
| /linux-6.15/fs/afs/ |
| H A D | Kconfig | 17 bool "AFS dynamic debugging"
20 Say Y here to make runtime controllable debugging messages appear.
34 bool "AFS server cursor debugging"
|
| /linux-6.15/scripts/ |
| H A D | checkversion.pl | 13 my $debugging;
66 if ($debugging) {
|
| /linux-6.15/fs/cachefiles/ |
| H A D | Kconfig | 18 This permits debugging to be dynamically enabled in the filesystem
19 caching on files module. If this is set, the debugging output may be
21 by including a debugging specifier in /etc/cachefilesd.conf.
|
| /linux-6.15/block/ |
| H A D | Kconfig.iosched | 41 bool "BFQ IO controller debugging"
44 Enable some debugging help. Currently it exports additional stat
45 files in a cgroup which can be useful for debugging.
|
| /linux-6.15/arch/nios2/ |
| H A D | Kconfig.debug | 4 bool "Activate early kernel debugging"
10 This is useful for kernel debugging when your machine crashes very
|
| /linux-6.15/Documentation/firmware-guide/acpi/ |
| H A D | method-tracing.rst | 26 ACPICA subsystem provides debugging outputs when CONFIG_ACPI_DEBUG is
27 enabled. The debugging messages which are deployed via
34 evaluations, the quantity of the debugging outputs may still be too
101 interpretation, thus can aid issue debugging and performance tuning. Note
200 ACPICA debugging messages matching "trace_debug_layer/trace_debug_level"
206 ACPICA debugging messages matching "trace_debug_layer/trace_debug_level"
212 ACPICA debugging messages matching "trace_debug_layer/trace_debug_level"
218 ACPICA debugging messages matching "trace_debug_layer/trace_debug_level"
224 ACPICA debugging messages matching "trace_debug_layer/trace_debug_level"
|
| /linux-6.15/drivers/memstick/ |
| H A D | Kconfig | 17 bool "MemoryStick debugging"
20 say N here. This enables MemoryStick core and driver debugging.
|
| /linux-6.15/drivers/infiniband/hw/mthca/ |
| H A D | Kconfig | 11 bool "Verbose debugging output" if EXPERT
15 This option causes debugging code to be compiled into the
|
| /linux-6.15/drivers/net/wireless/zydas/zd1211rw/ |
| H A D | Kconfig | 14 bool "ZyDAS ZD1211 debugging"
17 ZD1211 debugging messages. Choosing Y will result in additional debug
|
| /linux-6.15/Documentation/core-api/ |
| H A D | debugging-via-ohci1394.rst | 2 Using physical DMA provided by OHCI-1394 FireWire controllers for debugging
34 Together with a early initialization of the OHCI-1394 controller for debugging,
37 fails to boot and other means for debugging (serial port) are either not
44 DMA by default, which is more secure but not suitable for remote debugging.
53 Remote debugging over FireWire early on boot) and pass the parameter
147 4) Prepare for debugging with early OHCI-1394 initialization:
162 With the FireWire cable connected, the OHCI-1394 driver on the debugging
166 Then, on the debugging host, run firescope, for example by using -A::
|