Searched refs:debugging (Results 1 – 25 of 408) sorted by relevance
12345678910>>...17
| /Linux-v4.19/arch/arm/ |
| D | Kconfig.debug | 83 sometimes helpful for debugging but serves no purpose on a
97 bool "Kernel low-level debugging functions (read help!)"
101 in the kernel. This is helpful if you are debugging code that
110 prompt "Kernel low-level debugging port"
114 bool "Kernel low-level debugging messages via Alpine UART0"
118 Say Y here if you want kernel low-level debugging support
122 bool "Kernel low-level debugging via asm9260 UART"
143 bool "Kernel low-level debugging on AT91RM9200, AT91SAM9 DBGU"
147 Say Y here if you want kernel low-level debugging support
153 bool "Kernel low-level debugging on AT91SAM{9263,9G45,A5D3} DBGU"
[all …]
|
| /Linux-v4.19/net/mac80211/ |
| D | Kconfig | 108 collect all debugging messages, independent of
116 bool "Select mac80211 debugging features"
127 easier debugging of problems in the transmit and receive
138 bool "Verbose debugging output"
142 many debugging messages. It should not be selected
153 debugging messages for the managed-mode MLME. It
160 bool "Verbose station debugging"
164 debugging messages for station addition/removal.
169 bool "Verbose HT debugging"
181 bool "Verbose OCB debugging"
[all …]
|
| /Linux-v4.19/arch/powerpc/ |
| D | Kconfig.debug | 147 bool "Early debugging (dangerous)"
149 Say Y to enable some early debugging facilities that may be available
157 prompt "Early debugging console"
160 Use the selected console for early debugging. Careful, if you
161 enable debugging for the wrong type of machine your kernel
168 Select this to enable early debugging for a machine using BootX
175 Select this to enable early debugging for a machine with a HVC
182 Select this to enable early debugging for a machine with a HVSI
189 Select this to enable early debugging for Apple G5 machines.
195 Select this to enable early debugging via the RTAS panel.
[all …]
|
| /Linux-v4.19/net/dccp/ccids/ |
| D | Kconfig | 4 bool "CCID-2 debugging messages"
6 Enable CCID-2 specific debugging messages.
8 The debugging output can additionally be toggled by setting the
39 bool "CCID-3 debugging messages"
42 Enable CCID-3 specific debugging messages.
44 The debugging output can additionally be toggled by setting the
|
| /Linux-v4.19/fs/jbd2/ |
| D | Kconfig | 22 bool "JBD2 (ext4) debugging support"
27 allows you to enable debugging output while the system is running,
29 By default, the debugging output will be turned off.
31 If you select Y here, then you will be able to turn on debugging
33 number between 1 and 5. The higher the number, the more debugging
34 output is generated. To turn debugging off again, do
|
| /Linux-v4.19/drivers/infiniband/ulp/ipoib/ |
| D | Kconfig | 27 bool "IP-over-InfiniBand debugging" if EXPERT
31 This option causes debugging code to be compiled into the
37 debugfs, which contains files that expose debugging
42 bool "IP-over-InfiniBand data path debugging"
45 This option compiles debugging code into the data path
48 turned off, this debugging code will have some performance
|
| /Linux-v4.19/fs/fscache/ |
| D | Kconfig | 25 debugging purposes. Saying 'Y' here is recommended.
42 useful for debugging purposes. Saying 'N' here is recommended.
50 This permits debugging to be dynamically enabled in the local caching
51 management module. If this is set, the debugging output may be
57 bool "Maintain global object list for debugging purposes"
61 retrieved through /proc/fs/fscache/objects for debugging purposes
|
| /Linux-v4.19/drivers/gpu/drm/i915/ |
| D | Kconfig.debug | 19 bool "Enable additional driver debugging"
35 Choose this option to turn on extra driver debugging that may affect
72 Enable additional and verbose debugging output that will spam
73 ordinary tests, but may be vital for post-mortem debugging when
81 bool "Enable additional driver debugging for fence objects"
86 Choose this option to turn on extra driver debugging that may affect
94 bool "Enable additional driver debugging for detecting dependency cycles"
98 Choose this option to turn on extra driver debugging that may affect
106 bool "Enable additional driver debugging for GuC"
110 Choose this option to turn on extra driver debugging that may affect
|
| /Linux-v4.19/Documentation/power/ |
| D | drivers-testing.txt | 17 testing the new driver. Please see Documentation/power/basic-pm-debugging.txt
18 for more information about the debugging of suspend/resume functionality.
26 (see: Documentation/power/basic-pm-debugging.txt, 1).
29 "platform" modes (see: Documentation/power/basic-pm-debugging.txt, 1).
37 e) Try the test modes of suspend (see: Documentation/power/basic-pm-debugging.txt,
42 (see: Documentation/power/basic-pm-debugging.txt, 2).
|
| /Linux-v4.19/arch/unicore32/ |
| D | Kconfig.debug | 8 This is useful for kernel debugging when your machine crashes very
16 bool "Kernel low-level debugging functions"
20 in the kernel. This is helpful if you are debugging code that
24 bool "Kernel low-level debugging via On-Chip-Debugger"
|
| /Linux-v4.19/Documentation/pti/ |
| D | pti_intel_mid.txt | 12 pti.c is the driver that enables various debugging features
16 debugging data from a modem. Although n_tracerouter
26 An example debugging usage for this driver system:
28 a console device to further capture debugging messages to PTI.
29 *Hook /dev/ttyPTI1 to modem debugging data to write to PTI HW.
31 *Hook /dev/pti to a user-level debugging application for writing
34 debugging to PTI by first requesting a PTI write address via
|
| /Linux-v4.19/fs/cachefiles/ |
| D | Kconfig | 17 This permits debugging to be dynamically enabled in the filesystem
18 caching on files module. If this is set, the debugging output may be
20 by including a debugging specifier in /etc/cachefilesd.conf.
36 useful for debugging purposes. Saying 'N' here is recommended.
|
| /Linux-v4.19/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-v4.19/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-v4.19/Documentation/parisc/ |
| D | 00-INDEX | 3 debugging
4 - some debugging hints for real-mode code
|
| /Linux-v4.19/fs/ntfs/ |
| D | Kconfig | 30 bool "NTFS debugging support"
35 performed by the driver as well as additional debugging messages to
36 be written to the system log. Note that debugging messages are
40 you can enable debugging messages by doing (as root):
44 If you leave debugging messages disabled, this results in little
49 debugging messages while the misbehaviour was occurring.
|
| /Linux-v4.19/Documentation/ |
| D | debugging-modules.txt | 10 In the past a debugging message which would fill people's logs was
11 emitted. This debugging message has been removed. The correct way
12 of debugging module problems is something like this:
|
| /Linux-v4.19/scripts/ |
| D | checkversion.pl | 13 my $debugging;
62 if ($debugging) {
|
| /Linux-v4.19/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:
52 O Switch debugging off for caches that would have
54 - Switch all debugging off (useful if the kernel is
[all …]
|
| /Linux-v4.19/arch/nios2/ |
| D | Kconfig.debug | 7 bool "Activate early kernel debugging"
12 This is useful for kernel debugging when your machine crashes very
|
| /Linux-v4.19/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-v4.19/Documentation/acpi/ |
| D | method-tracing.txt | 18 ACPICA subsystem provides debugging outputs when CONFIG_ACPI_DEBUG is
19 enabled. The debugging messages which are deployed via
26 evaluations, the quantity of the debugging outputs may still be too
83 interpretion, thus can aid issue debugging and performance tuning. Note
160 ACPICA debugging messages matching
165 ACPICA debugging messages matching
170 ACPICA debugging messages matching
175 ACPICA debugging messages matching
180 ACPICA debugging messages matching
|
| /Linux-v4.19/drivers/memstick/ |
| D | Kconfig | 16 bool "MemoryStick debugging"
19 say N here. This enables MemoryStick core and driver debugging.
|
| /Linux-v4.19/drivers/net/wireless/zydas/zd1211rw/ |
| D | Kconfig | 13 bool "ZyDAS ZD1211 debugging"
16 ZD1211 debugging messages. Choosing Y will result in additional debug
|
| /Linux-v4.19/drivers/infiniband/hw/mthca/ |
| D | Kconfig | 10 bool "Verbose debugging output" if EXPERT
14 This option causes debugging code to be compiled into the
|
12345678910>>...17
