Searched full:debug (Results 1 – 25 of 423) sorted by relevance
12345678910>>...17
| /Documentation/arch/s390/ |
| D | s390dbf.rst | 2 S390 Debug Feature
6 - arch/s390/kernel/debug.c
7 - arch/s390/include/asm/debug.h
11 The goal of this feature is to provide a kernel debug logging API
13 (e.g. device drivers) can have one separate debug log.
14 One purpose of this is to inspect the debug logs after a production system crash
18 it is possible to look at the debug logs on a live system via the Linux
21 The debug feature may also very useful for kernel and driver development.
25 Kernel components (e.g. device drivers) can register themselves at the debug
28 debug log for the caller. For each debug log exists a number of debug areas
[all …]
|
| D | common_io.rst | 13 Enable logging of debug information in case of ccw device timeouts.
121 * /sys/kernel/debug/s390dbf/cio_*/ (S/390 debug feature)
123 Some views generated by the debug feature to hold various debug outputs.
125 - /sys/kernel/debug/s390dbf/cio_crw/sprintf
129 - /sys/kernel/debug/s390dbf/cio_msg/sprintf
130 Various debug messages from the common I/O-layer.
132 - /sys/kernel/debug/s390dbf/cio_trace/hex_ascii
138 /sys/kernel/debug/s390dbf/cio_*/level a number between 0 and 6; see the
139 documentation on the S/390 debug feature (Documentation/arch/s390/s390dbf.rst)
|
| /Documentation/trace/coresight/ |
| D | coresight-cpu-debug.rst | 2 Coresight CPU Debug Module
11 Coresight CPU debug module is defined in ARMv8-a architecture reference manual
12 (ARM DDI 0487A.k) Chapter 'Part H: External debug', the CPU can integrate
13 debug module and it is mainly used for two modes: self-hosted debug and
14 external debug. Usually the external debug mode is well known as the external
16 explore debugging method which rely on self-hosted debug mode, this document
19 The debug module provides sample-based profiling extension, which can be used
21 every CPU has one dedicated debug module to be connected. Based on self-hosted
22 debug mechanism, Linux kernel can access these related registers from mmio
36 - At the time this documentation was written, the debug driver mainly relies on
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,coresight-cpu-debug.yaml | 4 $id: http://devicetree.org/schemas/arm/arm,coresight-cpu-debug.yaml#
7 title: CoreSight CPU Debug Component
16 CoreSight CPU debug component are compliant with the ARMv8 architecture
17 reference manual (ARM DDI 0487A.k) Chapter 'Part H: External debug'. The
18 external debug module is mainly used for two modes: self-hosted debug and
19 external debug, and it can be accessed from mmio region from Coresight and
20 eventually the debug module connects with CPU for debugging. And the debug
23 has one dedicated debug module to be connected.
29 const: arm,coresight-cpu-debug
39 - const: arm,coresight-cpu-debug
[all …]
|
| /Documentation/driver-api/usb/ |
| D | usb3-debug-port.rst | 2 USB3 debug port
11 This is a HOWTO for using the USB3 debug port on x86 systems.
14 debug port, you need to::
16 1) check whether any USB3 debug port is available in
24 The xHCI debug capability (DbC) is an optional but standalone
28 When DbC is initialized and enabled, it will present a debug
29 device through the debug port (normally the first USB3
30 super-speed port). The debug device is fully compliant with
32 performance full-duplex serial link between the debug target
33 (the system under debugging) and a debug host.
[all …]
|
| /Documentation/devicetree/bindings/soc/socionext/ |
| D | socionext,uniphier-soc-glue-debug.yaml | 4 $id: http://devicetree.org/schemas/soc/socionext/socionext,uniphier-soc-glue-debug.yaml#
7 title: Socionext UniPhier SoC-glue logic debug part
13 SoC-glue logic debug part implemented on Socionext UniPhier SoCs is
15 system components for debug and monitor use.
21 - socionext,uniphier-ld4-soc-glue-debug
22 - socionext,uniphier-pro4-soc-glue-debug
23 - socionext,uniphier-pro5-soc-glue-debug
24 - socionext,uniphier-pxs2-soc-glue-debug
25 - socionext,uniphier-sld8-soc-glue-debug
26 - socionext,uniphier-ld11-soc-glue-debug
[all …]
|
| /Documentation/ABI/testing/ |
| D | debugfs-hisi-hpre | 1 What: /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/regs
4 Description: Dump debug registers from the HPRE cluster.
7 What: /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/cluster_ctrl
11 and then we can read the debug information of the core.
14 What: /sys/kernel/debug/hisi_hpre/<bdf>/rdclr_en
17 Description: HPRE cores debug registers read clear control. 1 means enable
23 What: /sys/kernel/debug/hisi_hpre/<bdf>/current_qm
30 What: /sys/kernel/debug/hisi_hpre/<bdf>/alg_qos
40 What: /sys/kernel/debug/hisi_hpre/<bdf>/regs
43 Description: Dump debug registers from the HPRE.
[all …]
|
| D | debugfs-hisi-zip | 1 What: /sys/kernel/debug/hisi_zip/<bdf>/comp_core[01]/regs
4 Description: Dump of compression cores related debug registers.
7 What: /sys/kernel/debug/hisi_zip/<bdf>/decomp_core[0-5]/regs
10 Description: Dump of decompression cores related debug registers.
13 What: /sys/kernel/debug/hisi_zip/<bdf>/clear_enable
16 Description: Compression/decompression core debug registers read clear
22 What: /sys/kernel/debug/hisi_zip/<bdf>/current_qm
29 What: /sys/kernel/debug/hisi_zip/<bdf>/alg_qos
39 What: /sys/kernel/debug/hisi_zip/<bdf>/qm/regs
42 Description: Dump of QM related debug registers.
[all …]
|
| D | debugfs-hisi-sec | 1 What: /sys/kernel/debug/hisi_sec2/<bdf>/clear_enable
5 the SEC debug registers.
9 What: /sys/kernel/debug/hisi_sec2/<bdf>/current_qm
17 What: /sys/kernel/debug/hisi_sec2/<bdf>/alg_qos
27 What: /sys/kernel/debug/hisi_sec2/<bdf>/qm/qm_regs
30 Description: Dump of QM related debug registers.
32 has one debug register.
34 What: /sys/kernel/debug/hisi_sec2/<bdf>/qm/current_q
38 queue to show its debug registers in above 'regs'.
41 What: /sys/kernel/debug/hisi_sec2/<bdf>/qm/clear_enable
[all …]
|
| D | sysfs-bus-pci-drivers-xhci_hcd | 6 USB3 controllers) are often implemented with the Debug
7 Capability (DbC). It can present a debug device which
10 serial link for debug purpose.
12 The DbC debug device shares a root port with xHCI host.
14 to the Debug Capability. Otherwise, it will be assigned
32 presented in the USB device descriptor by this xhci debug
34 Value can only be changed while debug capability (DbC) is in
45 presented in the USB device descriptor by this xhci debug
47 Value can only be changed while debug capability (DbC) is in
57 presented in the USB device descriptor by this xhci debug
[all …]
|
| D | debugfs-driver-habanalabs | 1 What: /sys/kernel/debug/habanalabs/hl<n>/addr
11 What: /sys/kernel/debug/habanalabs/hl<n>/clk_gate
17 What: /sys/kernel/debug/habanalabs/hl<n>/command_buffers
24 What: /sys/kernel/debug/habanalabs/hl<n>/command_submission
31 What: /sys/kernel/debug/habanalabs/hl<n>/command_submission_jobs
38 What: /sys/kernel/debug/habanalabs/hl<n>/data32
53 What: /sys/kernel/debug/habanalabs/hl<n>/data64
68 What: /sys/kernel/debug/habanalabs/hl<n>/data_dma
86 What: /sys/kernel/debug/habanalabs/hl<n>/device
94 What: /sys/kernel/debug/habanalabs/hl<n>/device_release_watchdog_timeout
[all …]
|
| D | debugfs-driver-genwqe | 1 What: /sys/kernel/debug/genwqe/genwqe<n>_card/ddcb_info
6 What: /sys/kernel/debug/genwqe/genwqe<n>_card/curr_regs
12 What: /sys/kernel/debug/genwqe/genwqe<n>_card/curr_dbg_uid0
18 What: /sys/kernel/debug/genwqe/genwqe<n>_card/curr_dbg_uid1
24 What: /sys/kernel/debug/genwqe/genwqe<n>_card/curr_dbg_uid2
30 What: /sys/kernel/debug/genwqe/genwqe<n>_card/prev_regs
37 What: /sys/kernel/debug/genwqe/genwqe<n>_card/prev_dbg_uid0
43 What: /sys/kernel/debug/genwqe/genwqe<n>_card/prev_dbg_uid1
49 What: /sys/kernel/debug/genwqe/genwqe<n>_card/prev_dbg_uid2
55 What: /sys/kernel/debug/genwqe/genwqe<n>_card/info
[all …]
|
| D | sysfs-driver-st | 6 This file allows you to turn debug output from the st driver
8 Note that debug output requires that the module be compiled
9 with the #define DEBUG set to a non-zero value (this is the
10 default). If DEBUG is set to 0 then this file will not
11 appear in sysfs as its presence is conditional upon debug
|
| D | debugfs-scmi | 1 What: /sys/kernel/debug/scmi/<n>/instance_name
6 all the debugfs accessors rooted at /sys/kernel/debug/scmi/<n>,
11 What: /sys/kernel/debug/scmi/<n>/atomic_threshold_us
22 What: /sys/kernel/debug/scmi/<n>/transport/type
30 What: /sys/kernel/debug/scmi/<n>/transport/is_atomic
38 What: /sys/kernel/debug/scmi/<n>/transport/max_rx_timeout_ms
46 What: /sys/kernel/debug/scmi/<n>/transport/max_msg_size
54 What: /sys/kernel/debug/scmi/<n>/transport/tx_max_msg
63 What: /sys/kernel/debug/scmi/<n>/transport/rx_max_msg
|
| D | debugfs-driver-dcc | 1 What: /sys/kernel/debug/dcc/.../ready
9 What: /sys/kernel/debug/dcc/.../trigger
17 What: /sys/kernel/debug/dcc/.../config_reset
27 What: /sys/kernel/debug/dcc/.../[list-number]/config
45 echo R <addr> <n> <bus> >/sys/kernel/debug/dcc/../[list-number]/config
65 echo W <addr> <n> <bus type> > /sys/kernel/debug/dcc/../[list-number]/config
82 echo RW <addr> <n> <mask> > /sys/kernel/debug/dcc/../[list-number]/config
99 … echo L <loop count> <address count> <address>... > /sys/kernel/debug/dcc/../[list-number]/config
112 What: /sys/kernel/debug/dcc/.../[list-number]/enable
|
| D | ppc-memtrace | 1 What: /sys/kernel/debug/powerpc/memtrace
9 What: /sys/kernel/debug/powerpc/memtrace/enable
22 What: /sys/kernel/debug/powerpc/memtrace/<node-id>
29 What: /sys/kernel/debug/powerpc/memtrace/<node-id>/size
35 What: /sys/kernel/debug/powerpc/memtrace/<node-id>/start
41 What: /sys/kernel/debug/powerpc/memtrace/<node-id>/trace
|
| D | debugfs-cros-ec | 1 What: /sys/kernel/debug/<cros-ec-device>/console_log
10 What: /sys/kernel/debug/<cros-ec-device>/panicinfo
18 What: /sys/kernel/debug/<cros-ec-device>/pdinfo
22 This file provides the port role, muxes and power debug
27 What: /sys/kernel/debug/<cros-ec-device>/uptime
36 What: /sys/kernel/debug/<cros-ec-device>/last_resume_result
58 What: /sys/kernel/debug/<cros-ec-device>/suspend_timeout_ms
|
| /Documentation/admin-guide/ |
| D | btmrvl.rst | 10 Path: /debug/btmrvl/config/
27 echo 0xff80 > /debug/btmrvl/config/gpiogap
28 echo 1 > /debug/btmrvl/config/hscfgcmd
31 echo 0x03ff > /debug/btmrvl/config/gpiogap
32 echo 1 > /debug/btmrvl/config/hscfgcmd
45 echo 1 > /debug/btmrvl/config/psmode
46 echo 1 > /debug/btmrvl/config/pscmd
49 echo 0 > /debug/btmrvl/config/psmode
50 echo 1 > /debug/btmrvl/config/pscmd
64 echo 1 > /debug/btmrvl/config/hsmode
[all …]
|
| D | dynamic-debug-howto.rst | 1 Dynamic debug
8 Dynamic debug allows you to dynamically enable/disable kernel
9 debug-print code to obtain additional kernel information.
12 debug. You'll need root access (sudo su) to use this.
14 Dynamic debug provides:
29 Viewing Dynamic Debug Behaviour
46 Controlling dynamic debug Behaviour
70 also under the mount-dir, typically ``/sys/kernel/debug/``.
163 The given string is searched for in the dynamic debug format
184 class DRM_UT_KMS # a DRM.debug category
[all …]
|
| /Documentation/gpu/amdgpu/display/ |
| D | dc-debug.rst | 2 Display Core Debug tools
10 information. In general, you can enable this debug option by using::
12 echo <N> > /sys/kernel/debug/dri/0/amdgpu_dm_visual_confirm
15 wants to enable, you will see some of these debug cases in the following
18 Multiple Planes Debug
21 If you want to enable or debug multiple planes in a specific user-space
22 application, you can leverage a debug feature named visual confirm. For
25 echo 1 > /sys/kernel/debug/dri/0/amdgpu_dm_visual_confirm
48 Pipe Split Debug
51 Sometimes we need to debug if DCN is splitting pipes correctly, and visual
[all …]
|
| /Documentation/fault-injection/ |
| D | fault-injection.rst | 40 debugfs entries under /sys/kernel/debug/mmc0/fail_mmc_request
46 under /sys/kernel/debug/fail_function. No boot option supported.
51 debugfs entries under /sys/kernel/debug/nvme*/fault_inject. The default
73 - /sys/kernel/debug/fail*/probability:
81 /sys/kernel/debug/fail*/interval for such testcases.
83 - /sys/kernel/debug/fail*/interval:
91 - /sys/kernel/debug/fail*/times:
96 - /sys/kernel/debug/fail*/space:
102 - /sys/kernel/debug/fail*/verbose
109 to debug the problems revealed by fault injection.
[all …]
|
| /Documentation/arch/x86/ |
| D | earlyprintk.rst | 8 USB2 Debug port key and a debug cable, on x86 systems.
10 You need two computers, the 'USB debug key' special gadget and
13 [host/target] <-------> [USB debug key] <-------> [client/console]
18 a) Host/target system needs to have USB debug port capability.
20 You can check this capability by looking at a 'Debug port' bit in
35 Capabilities: [58] Debug port: BAR=1 offset=00a0
42 If your system does not list a debug port capability then you probably
43 won't be able to use the USB debug key.
45 b) You also need a NetChip USB debug cable/key:
55 debug port on the "host/target" system. You cannot use a USB hub in
[all …]
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | dcsr.txt | 2 Debug Control and Status Register (DCSR) Binding
11 Debug Control and Status Register Memory Map
17 debug blocks defined within this memory space.
80 two interrupt signals based on debug event sources within the SoC.
166 CoreNet Debug Controller
169 the CoreNet Debug controller.
184 The CoreNet Debug controller occupies two regions in the DCSR space
187 The first register range describes the CoreNet Debug Controller
190 The second register range describes the CoreNet Debug Controller
191 functionality to trigger event notifications and debug traces.
[all …]
|
| /Documentation/dev-tools/ |
| D | kmemleak.rst | 8 reported via /sys/kernel/debug/kmemleak. A similar method is used by the
20 # mount -t debugfs nodev /sys/kernel/debug/
24 # cat /sys/kernel/debug/kmemleak
28 # echo scan > /sys/kernel/debug/kmemleak
32 # echo clear > /sys/kernel/debug/kmemleak
34 New leaks will then come up upon reading ``/sys/kernel/debug/kmemleak``
42 ``/sys/kernel/debug/kmemleak`` file. The following parameters are supported:
109 /sys/kernel/debug/kmemleak
120 Upon initial bootup your /sys/kernel/debug/kmemleak output page may be
124 /sys/kernel/debug/kmemleak output. By issuing a 'scan' after a 'clear'
[all …]
|
| /Documentation/networking/ |
| D | netif-msg.rst | 18 integer variable that controls the debug message level. The message
37 were consistently renamed to "debug" and allowed to be set as a module
53 - Retaining the per-driver integer variable "debug" as a module
59 1 << debug
63 debug < 0 ? 0 : 1 << min(sizeof(int)-1, debug)
67 if (debug > 1)
|
12345678910>>...17