Home
last modified time | relevance | path

Searched refs:debugging (Results 1 – 25 of 527) sorted by relevance

12345678910>>...22

/linux/arch/arm/
A DKconfig.debug125 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"
251 bool "Kernel low-level debugging on BCM IPROC UART3"
270 bool "Kernel low-level debugging on BCM63XX UART"
687 bool "Kernel low-level debugging via OMAP1 UART1"
695 bool "Kernel low-level debugging via OMAP1 UART2"
703 bool "Kernel low-level debugging via OMAP1 UART3"
[all …]
/linux/net/mac80211/
A DKconfig111 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/drivers/gpu/drm/xe/
A DKconfig.debug20 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/arch/powerpc/
A DKconfig.debug169 bool "Early debugging (dangerous)"
179 prompt "Early debugging console"
183 enable debugging for the wrong type of machine your kernel
217 Select this to enable early debugging via the RTAS panel.
224 Select this to enable early debugging via the RTAS console.
230 Select this to enable early debugging for Maple.
236 Select this to enable early debugging for PA Semi.
240 bool "Early serial debugging for IBM/AMCC 44x CPUs"
251 Select this to enable early debugging for Freescale chips
256 bool "Early debugging through the USB Gecko adapter"
[all …]
/linux/fs/jbd2/
A DKconfig23 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/
A DKconfig5 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/
A DKconfig28 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/
A Ddrivers-testing.rst21 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/Documentation/driver-api/usb/
A Dusb3-debug-port.rst13 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/drivers/gpu/drm/i915/
A DKconfig.debug37 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/fs/netfs/
A DKconfig23 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/
A Dkdb_cmds7 # Standard debugging information for first level support, just type archkdb
10 defcmd dumpcommon "" "Common kdb debugging"
20 defcmd dumpall "" "First line debugging"
/linux/fs/afs/
A DKconfig17 bool "AFS dynamic debugging"
20 Say Y here to make runtime controllable debugging messages appear.
34 bool "AFS server cursor debugging"
/linux/scripts/
A Dcheckversion.pl13 my $debugging;
66 if ($debugging) {
/linux/fs/cachefiles/
A DKconfig18 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/block/
A DKconfig.iosched41 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/arch/nios2/
A DKconfig.debug4 bool "Activate early kernel debugging"
10 This is useful for kernel debugging when your machine crashes very
/linux/Documentation/firmware-guide/acpi/
A Dmethod-tracing.rst26 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/drivers/memstick/
A DKconfig17 bool "MemoryStick debugging"
20 say N here. This enables MemoryStick core and driver debugging.
/linux/drivers/net/wireless/zydas/zd1211rw/
A DKconfig14 bool "ZyDAS ZD1211 debugging"
17 ZD1211 debugging messages. Choosing Y will result in additional debug
/linux/drivers/infiniband/hw/mthca/
A DKconfig11 bool "Verbose debugging output" if EXPERT
15 This option causes debugging code to be compiled into the
/linux/Documentation/core-api/
A Ddebugging-via-ohci1394.rst2 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/Documentation/mm/
A Dslub.rst8 SLUB can enable debugging only for selected slabs in order to avoid
13 to the kernel command line. That will enable full debugging for
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
85 switch off debugging for such caches by default, use::
91 kmalloc. All other slabs will not get any debugging enabled::
306 will be used (unlike full debugging).
[all …]
/linux/net/
A DKconfig.debug9 Enable debugging feature to track device references.
18 Enable debugging feature to track netns references.
/linux/arch/arm64/
A DKconfig.debug13 bool "UEFI debugging"
15 Enable this option to include EFI specific debugging features into

Completed in 40 milliseconds

12345678910>>...22