| /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/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/net/dccp/ccids/ |
| H A D | Kconfig | |
| /linux/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/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/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/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/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/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/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/Documentation/process/debugging/ |
| 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/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/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/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/scripts/ |
| H A D | checkversion.pl | 13 my $debugging;
66 if ($debugging) {
|
| /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/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/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/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/drivers/memstick/ |
| H A D | Kconfig | 17 bool "MemoryStick debugging"
20 say N here. This enables MemoryStick core and driver debugging.
|
| /linux/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/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/drivers/net/wireless/ath/ath5k/ |
| H A D | Kconfig | 24 bool "Atheros 5xxx debugging"
27 Atheros 5xxx debugging messages.
49 option if you are interested in debugging the driver.
|
| /linux/drivers/usb/dwc2/ |
| H A D | Kconfig | 70 Say Y here to enable debugging messages in the DWC2 Driver.
76 Say Y here to enable verbose debugging messages in the DWC2 Driver.
92 Say N here to disable (verbose) debugging messages to be
93 logged for periodic transfers. This allows better debugging of
|
| /linux/arch/arm64/ |
| H A D | Kconfig.debug | 13 bool "UEFI debugging"
15 Enable this option to include EFI specific debugging features into
|