Searched refs:debugging (Results 1 – 25 of 436) sorted by relevance
12345678910>>...18
| /Linux-v5.10/arch/arm/ |
| D | Kconfig.debug | 90 sometimes helpful for debugging but serves no purpose on a
104 bool "Kernel low-level debugging functions (read help!)"
108 in the kernel. This is helpful if you are debugging code that
117 prompt "Kernel low-level debugging port"
121 bool "Kernel low-level debugging messages via Alpine UART0"
125 Say Y here if you want kernel low-level debugging support
129 bool "Kernel low-level debugging via asm9260 UART"
150 bool "Kernel low-level debugging on AT91RM9200, AT91SAM9, SAM9X60 DBGU"
154 Say Y here if you want kernel low-level debugging support
160 bool "Kernel low-level debugging on AT91SAM{9263,9G45,A5D3} DBGU"
[all …]
|
| /Linux-v5.10/net/mac80211/ |
| D | Kconfig | 93 collect all debugging messages, independent of
101 bool "Select mac80211 debugging features"
112 easier debugging of problems in the transmit and receive
123 bool "Verbose debugging output"
127 many debugging messages. It should not be selected
138 debugging messages for the managed-mode MLME. It
145 bool "Verbose station debugging"
149 debugging messages for station addition/removal.
154 bool "Verbose HT debugging"
166 bool "Verbose OCB debugging"
[all …]
|
| /Linux-v5.10/arch/powerpc/ |
| D | Kconfig.debug | 149 bool "Early debugging (dangerous)"
151 Say Y to enable some early debugging facilities that may be available
159 prompt "Early debugging console"
162 Use the selected console for early debugging. Careful, if you
163 enable debugging for the wrong type of machine your kernel
170 Select this to enable early debugging for a machine using BootX
177 Select this to enable early debugging for a machine with a HVC
184 Select this to enable early debugging for a machine with a HVSI
191 Select this to enable early debugging for Apple G5 machines.
197 Select this to enable early debugging via the RTAS panel.
[all …]
|
| /Linux-v5.10/fs/jbd2/ |
| D | Kconfig | 23 bool "JBD2 (ext4) debugging support"
28 allows you to enable debugging output while the system is running,
30 By default, the debugging output will be turned off.
32 If you select Y here, then you will be able to turn on debugging
34 number between 1 and 5. The higher the number, the more debugging
35 output is generated. To turn debugging off again, do
|
| /Linux-v5.10/net/dccp/ccids/ |
| 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-v5.10/drivers/infiniband/ulp/ipoib/ |
| 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-v5.10/fs/fscache/ |
| D | Kconfig | 26 debugging purposes. Saying 'Y' here is recommended.
43 useful for debugging purposes. Saying 'N' here is recommended.
51 This permits debugging to be dynamically enabled in the local caching
52 management module. If this is set, the debugging output may be
58 bool "Maintain global object list for debugging purposes"
62 retrieved through /proc/fs/fscache/objects for debugging purposes
|
| /Linux-v5.10/drivers/gpu/drm/i915/ |
| D | Kconfig.debug | 20 bool "Enable additional driver debugging"
40 Choose this option to turn on extra driver debugging that may affect
90 Enable additional and verbose debugging output that will spam
91 ordinary tests, but may be vital for post-mortem debugging when
104 Enable additional and verbose debugging output that will spam
105 ordinary tests, but may be vital for post-mortem debugging when
113 bool "Enable additional driver debugging for fence objects"
118 Choose this option to turn on extra driver debugging that may affect
126 bool "Enable additional driver debugging for detecting dependency cycles"
130 Choose this option to turn on extra driver debugging that may affect
[all …]
|
| /Linux-v5.10/Documentation/power/ |
| 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-v5.10/fs/cachefiles/ |
| 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.
37 useful for debugging purposes. Saying 'N' here is recommended.
|
| /Linux-v5.10/Documentation/driver-api/usb/ |
| 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-v5.10/kernel/debug/kdb/ |
| 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-v5.10/Documentation/driver-api/ |
| D | pti_intel_mid.rst | 18 pti.c is the driver that enables various debugging features
22 debugging data from a modem. Although n_tracerouter
32 An example debugging usage for this driver system:
35 a console device to further capture debugging messages to PTI.
36 * Hook /dev/ttyPTI1 to modem debugging data to write to PTI HW.
38 * Hook /dev/pti to a user-level debugging application for writing
41 debugging to PTI by first requesting a PTI write address via
|
| /Linux-v5.10/fs/ntfs/ |
| D | Kconfig | 31 bool "NTFS debugging support"
36 performed by the driver as well as additional debugging messages to
37 be written to the system log. Note that debugging messages are
41 you can enable debugging messages by doing (as root):
45 If you leave debugging messages disabled, this results in little
50 debugging messages while the misbehaviour was occurring.
|
| /Linux-v5.10/fs/afs/ |
| D | Kconfig | 16 bool "AFS dynamic debugging"
19 Say Y here to make runtime controllable debugging messages appear.
33 bool "AFS server cursor debugging"
|
| /Linux-v5.10/scripts/ |
| D | checkversion.pl | 13 my $debugging;
62 if ($debugging) {
|
| /Linux-v5.10/block/ |
| 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-v5.10/arch/nios2/ |
| D | Kconfig.debug | 4 bool "Activate early kernel debugging"
9 This is useful for kernel debugging when your machine crashes very
|
| /Linux-v5.10/drivers/atm/ |
| D | Kconfig | 55 bool "Enable extended debugging"
58 Extended debugging records various events and displays that list
61 Note that extended debugging may create certain race conditions
170 bool "Enable extended debugging"
173 Extended debugging records various events and displays that list
176 Note that extended debugging may create certain race conditions
222 bool "Enable debugging messages"
225 Somewhat useful debugging messages are available. The choice of
240 for debugging or special applications only, so the safe answer is N.
257 bool "Enable debugging messages"
[all …]
|
| /Linux-v5.10/Documentation/firmware-guide/acpi/ |
| 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-v5.10/Documentation/vm/ |
| D | slub.rst | 9 slab caches. SLUB always includes full debugging but it is off by default.
10 SLUB can enable debugging only for selected slabs in order to avoid
14 In order to switch debugging on one can add an option ``slub_debug``
15 to the kernel command line. That will enable full debugging for
26 Some of the modes of operation of ``slabinfo`` require that slub debugging
28 available without debugging on and validation can only partially
29 be performed if debugging was not switched on.
35 debugging is enabled. Format:
58 O Switch debugging off for caches that would have
60 - Switch all debugging off (useful if the kernel is
[all …]
|
| /Linux-v5.10/drivers/memstick/ |
| D | Kconfig | 17 bool "MemoryStick debugging"
20 say N here. This enables MemoryStick core and driver debugging.
|
| /Linux-v5.10/drivers/net/wireless/zydas/zd1211rw/ |
| D | Kconfig | 14 bool "ZyDAS ZD1211 debugging"
17 ZD1211 debugging messages. Choosing Y will result in additional debug
|
| /Linux-v5.10/drivers/infiniband/hw/mthca/ |
| D | Kconfig | 11 bool "Verbose debugging output" if EXPERT
15 This option causes debugging code to be compiled into the
|
| /Linux-v5.10/Documentation/core-api/ |
| 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::
|
12345678910>>...18
