| /linux/arch/arm/ |
| H A D | Kconfig.debug | 98 sometimes helpful for debugging but serves no purpose on a
112 bool "Kernel low-level debugging functions (read help!)"
116 in the kernel. This is helpful if you are debugging code that
125 prompt "Kernel low-level debugging port"
129 bool "Kernel low-level debugging messages via Alpine UART0"
133 Say Y here if you want kernel low-level debugging support
137 bool "Kernel low-level debugging via asm9260 UART"
158 bool "Kernel low-level debugging on AT91RM9200, AT91SAM9, SAM9X60 DBGU"
162 Say Y here if you want kernel low-level debugging support
168 bool "Kernel low-level debugging on AT91SAM{9263,9G45,A5D3} DBGU"
[all …]
|
| /linux/net/mac80211/ |
| H A D | Kconfig | 103 collect all debugging messages, independent of
111 bool "Select mac80211 debugging features"
122 easier debugging of problems in the transmit and receive
133 bool "Verbose debugging output"
137 many debugging messages. It should not be selected
148 debugging messages for the managed-mode MLME. It
155 bool "Verbose station debugging"
159 debugging messages for station addition/removal.
164 bool "Verbose HT debugging"
176 bool "Verbose OCB debugging"
[all …]
|
| /linux/arch/powerpc/ |
| H A D | Kconfig.debug | 169 bool "Early debugging (dangerous)"
171 Say Y to enable some early debugging facilities that may be available
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
190 Select this to enable early debugging for a machine using BootX
197 Select this to enable early debugging for a machine with a HVC
204 Select this to enable early debugging for a machine with a HVSI
211 Select this to enable early debugging for Apple G5 machines.
217 Select this to enable early debugging via the RTAS panel.
[all …]
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-bus-vmbus | 71 Users: tools/hv/lsvmbus and other debugging tools
78 Users: Debugging tools
87 Users: Debugging tools
94 Users: Debugging tools
103 Users: Debugging tools
110 Users: Debugging tools
117 Users: Debugging tools
124 Users: Debugging tools
131 Users: Debugging tools
138 Users: Debugging tools and userspace drivers
[all …]
|
| /linux/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 SR-IOV debugging"
47 Enable extra SR-IOV debugging info.
81 Choose this option when debugging guc issues.
92 Choose this option when debugging error paths that
|
| /linux/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
167 bool "Enable additional driver debugging for detecting dependency cycles"
171 Choose this option to turn on extra driver debugging that may affect
[all …]
|
| /linux/Documentation/ABI/testing/ |
| H A D | debugfs-scmi | 9 Users: Debugging, any userspace test suite
20 Users: Debugging, any userspace test suite
28 Users: Debugging, any userspace test suite
36 Users: Debugging, any userspace test suite
44 Users: Debugging, any userspace test suite
52 Users: Debugging, any userspace test suite
61 Users: Debugging, any userspace test suite
70 Users: Debugging, any userspace test suite
|
| H A D | debugfs-scmi-raw | 14 Users: Debugging, any userspace test suite
32 Users: Debugging, any userspace test suite
43 Users: Debugging, any userspace test suite
54 Users: Debugging, any userspace test suite
66 Users: Debugging, any userspace test suite
90 Users: Debugging, any userspace test suite
117 Users: Debugging, any userspace test suite
|
| /linux/fs/jbd2/ |
| H A 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/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/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/drivers/usb/dwc2/ |
| H A D | Kconfig | 68 bool "Enable Debugging Messages"
70 Say Y here to enable debugging messages in the DWC2 Driver.
73 bool "Enable Verbose Debugging Messages"
76 Say Y here to enable verbose debugging messages in the DWC2 Driver.
88 bool "Enable Debugging Messages For Periodic Transfers"
92 Say N here to disable (verbose) debugging messages to be
93 logged for periodic transfers. This allows better debugging of
|
| /linux/kernel/configs/ |
| H A D | debug.config | 1 # Help: Debugging for CI systems and finding regressions
27 # Generic Kernel Debugging Instruments
43 # Networking Debugging
49 # Memory Debugging
95 # Lock Debugging (spinlocks, mutexes, etc...)
104 # RCU Debugging
|
| /linux/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/lib/ |
| H A D | Kconfig.debug | 130 Dynamic debugging is controlled via the 'dynamic_debug/control' file,
207 debugging but costs about 70-100K of memory.
212 bool "Kernel debugging"
245 that will include debugging info resulting in a larger kernel image.
256 Do not build the kernel with debugging information, which will
306 bool "Reduce debugging information"
308 If you say Y here gcc is instructed to generate less debugging
310 need full debugging information (like kgdb or systemtap) won't
311 be happy. But if you merely need debugging information to
331 bool "Compress debugging information with zlib"
[all …]
|
| /linux/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/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/drivers/atm/ |
| H A 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
192 bool "Enable debugging messages"
195 Somewhat useful debugging messages are available. The choice of
210 for debugging or special applications only, so the safe answer is N.
235 bool "Enable debugging messages"
238 Somewhat useful debugging messages are available. The choice of
292 int "Debugging level (0-3)"
296 Specifies the level of debugging messages issued by the driver.
[all …]
|
| /linux/Documentation/mm/ |
| H A D | slub.rst | 7 slab caches. SLUB always includes full debugging but it is off by default.
8 SLUB can enable debugging only for selected slabs in order to avoid
12 In order to switch debugging on one can add an option ``slab_debug``
13 to the kernel command line. That will enable full debugging for
24 Some of the modes of operation of ``slabinfo`` require that slub debugging
26 available without debugging on and validation can only partially
27 be performed if debugging was not switched on.
33 debugging is enabled. Format:
56 O Switch debugging off for caches that would have
58 - Switch all debugging off (useful if the kernel is
[all …]
|
| /linux/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/arch/powerpc/kvm/ |
| H A D | booke_emulate.c | 118 * (such as debugging).
146 * If userspace is debugging guest then guest in kvmppc_booke_emulate_mtspr()
157 * If userspace is debugging guest then guest in kvmppc_booke_emulate_mtspr()
169 * If userspace is debugging guest then guest in kvmppc_booke_emulate_mtspr()
180 * If userspace is debugging guest then guest in kvmppc_booke_emulate_mtspr()
192 * If userspace is debugging guest then guest in kvmppc_booke_emulate_mtspr()
203 * If userspace is debugging guest then guest in kvmppc_booke_emulate_mtspr()
214 * If userspace is debugging guest then guest in kvmppc_booke_emulate_mtspr()
229 * If userspace is debugging guest then guest in kvmppc_booke_emulate_mtspr()
240 * If userspace is debugging guest then guest in kvmppc_booke_emulate_mtspr()
[all …]
|
| /linux/fs/jffs2/ |
| H A D | Kconfig | 16 int "JFFS2 debugging verbosity (0 = quiet, 2 = noisy)"
20 This controls the amount of debugging messages produced by the JFFS2
22 testing and debugging, it's advisable to set it to one. This will
23 enable a few assertions and will print debugging messages at the
25 is unlikely to be useful - it enables extra debugging in certain
26 areas which at one point needed debugging, but when the bugs were
|
| /linux/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::
|
| /linux/sound/core/ |
| H A D | Kconfig | 197 Say Y here to enable extra-verbose debugging messages.
199 Let me repeat: it enables EXTRA-VERBOSE DEBUGGING messages.
203 bool "Enable PCM ring buffer overrun/underrun debugging"
207 Say Y to enable the PCM ring buffer overrun/underrun debugging.
223 bool "Enable debugging feature for control API"
226 Say Y to enable the debugging feature for ALSA control API.
242 Say Y if you are debugging via jack injection interface.
|
| /linux/drivers/usb/gadget/ |
| H A D | Kconfig | 50 bool "Debugging messages (DEVELOPMENT)"
53 Many controller and gadget drivers will print some debugging
57 debugging such a driver. Many drivers will emit so many
64 bool "Verbose debugging Messages (DEVELOPMENT)"
67 Many controller and gadget drivers will print verbose debugging
71 debugging such a driver. Many drivers will emit so many
78 bool "Debugging information files (DEVELOPMENT)"
82 debugging information in files such as /proc/driver/udc
89 bool "Debugging information files in debugfs (DEVELOPMENT)"
93 debugging information in files under /sys/kernel/debug/.
|