Home
last modified time | relevance | path

Searched full:debug (Results 1 – 25 of 3905) sorted by relevance

12345678910>>...157

/linux/Documentation/arch/s390/
H A Ds390dbf.rst2 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 …]
/linux/tools/testing/selftests/kvm/x86_64/
H A Ddebug_regs.c3 * KVM guest debug register tests
18 /* For testing data access debug BP */
83 struct kvm_guest_debug debug; in main() local
107 memset(&debug, 0, sizeof(debug)); in main()
108 debug.control = KVM_GUESTDBG_ENABLE | KVM_GUESTDBG_USE_SW_BP; in main()
109 vcpu_guest_debug_set(vcpu, &debug); in main()
112 run->debug.arch.exception == BP_VECTOR && in main()
113 run->debug.arch.pc == CAST_TO_RIP(sw_bp), in main()
115 run->exit_reason, run->debug.arch.exception, in main()
116 run->debug.arch.pc, CAST_TO_RIP(sw_bp)); in main()
[all …]
/linux/arch/s390/include/asm/
H A Ddebug.h3 * S/390 debug facility
18 #define DEBUG_MAX_LEVEL 6 /* debug levels range from 0 to 6 */
19 #define DEBUG_OFF_LEVEL -1 /* level where debug is switched off */
23 #define DEBUG_DEFAULT_LEVEL 3 /* initial debug level */
25 #define DEBUG_DIR_ROOT "s390dbf" /* name of debug root directory in proc fs */
30 #define __DEBUG_FEATURE_VERSION 3 /* version of debug feature */
106 /* Debug Feature API: */
124 * debug_level_enabled() - Returns true if debug events for the specified
127 * @id: handle for debug log
128 * @level: debug level
[all …]
/linux/Documentation/trace/coresight/
H A Dcoresight-cpu-debug.rst2 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 …]
/linux/arch/powerpc/kernel/ptrace/
H A Dptrace-adv.c13 task->thread.debug.dbcr0 &= ~DBCR0_BT; in user_enable_single_step()
14 task->thread.debug.dbcr0 |= DBCR0_IDM | DBCR0_IC; in user_enable_single_step()
25 task->thread.debug.dbcr0 &= ~DBCR0_IC; in user_enable_block_step()
26 task->thread.debug.dbcr0 = DBCR0_IDM | DBCR0_BT; in user_enable_block_step()
40 * And, after doing so, if all debug flags are off, turn in user_disable_single_step()
43 task->thread.debug.dbcr0 &= ~(DBCR0_IC | DBCR0_BT); in user_disable_single_step()
47 if (!DBCR_ACTIVE_EVENTS(task->thread.debug.dbcr0, in user_disable_single_step()
48 task->thread.debug.dbcr1)) { in user_disable_single_step()
50 * All debug events were off..... in user_disable_single_step()
52 task->thread.debug.dbcr0 &= ~DBCR0_IDM; in user_disable_single_step()
[all …]
/linux/drivers/gpu/drm/msm/dp/
H A Ddp_debug.c28 struct dp_debug_private *debug = seq->private; in dp_debug_show() local
33 if (!debug) in dp_debug_show()
36 drm_mode = &debug->panel->dp_mode.drm_mode; in dp_debug_show()
40 debug->panel->link_info.rate); in dp_debug_show()
42 debug->panel->link_info.num_lanes); in dp_debug_show()
44 debug->panel->link_info.capabilities); in dp_debug_show()
58 debug->panel->dp_mode.h_active_low, in dp_debug_show()
59 debug->panel->dp_mode.v_active_low); in dp_debug_show()
67 debug->panel->dp_mode.bpp); in dp_debug_show()
71 debug->link->sink_request); in dp_debug_show()
[all …]
/linux/Documentation/ABI/testing/
H A Ddebugfs-hisi-hpre1 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 …]
H A Ddebugfs-hisi-zip1 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 …]
H A Ddebugfs-hisi-sec1 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 …]
H A Ddebugfs-driver-habanalabs1 What: /sys/kernel/debug/accel/<parent_device>/addr
11 What: /sys/kernel/debug/accel/<parent_device>/clk_gate
17 What: /sys/kernel/debug/accel/<parent_device>/command_buffers
24 What: /sys/kernel/debug/accel/<parent_device>/command_submission
31 What: /sys/kernel/debug/accel/<parent_device>/command_submission_jobs
38 What: /sys/kernel/debug/accel/<parent_device>/data32
53 What: /sys/kernel/debug/accel/<parent_device>/data64
68 What: /sys/kernel/debug/accel/<parent_device>/data_dma
86 What: /sys/kernel/debug/accel/<parent_device>/device
94 What: /sys/kernel/debug/accel/<parent_device>/device_release_watchdog_timeout
[all …]
H A Ddebugfs-intel-iommu1 What: /sys/kernel/debug/iommu/intel/iommu_regset
11 $ sudo cat /sys/kernel/debug/iommu/intel/iommu_regset
46 What: /sys/kernel/debug/iommu/intel/ir_translation_struct
57 $ sudo cat /sys/kernel/debug/iommu/intel/ir_translation_struct
79 What: /sys/kernel/debug/iommu/intel/dmar_translation_struct
93 $ sudo cat /sys/kernel/debug/iommu/intel/dmar_translation_struct
117 What: /sys/kernel/debug/iommu/intel/invalidation_queue
128 $ sudo cat /sys/kernel/debug/iommu/intel/invalidation_queue
153 What: /sys/kernel/debug/iommu/intel/dmar_perf_latency
161 /sys/kernel/debug/iommu/intel/dmar_perf_latency
[all …]
H A Dsysfs-bus-pci-drivers-xhci_hcd6 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 …]
/linux/Documentation/driver-api/usb/
H A Dusb3-debug-port.rst2 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 …]
/linux/arch/arm/
H A DKconfig.debug90 In most cases, say N here, unless you are intending to debug the
140 Say Y here if you want the debug print routines to direct
198 Say Y here if you want the debug print routines to direct
255 Say Y here if you want the debug print routines to direct
265 This low level debug works for Broadcom
274 bool "Marvell Berlin SoC Debug UART"
282 bool "Use BRCMSTB UART for low-level debug"
285 Say Y here if you want the debug print routines to direct
297 Say Y here if you want the debug print routines to direct
304 Say Y here if you want the debug print routines to direct
[all …]
/linux/drivers/media/platform/rockchip/rkisp1/
H A Drkisp1-debug.c196 struct rkisp1_debug *debug = &rkisp1->debug; in rkisp1_debug_init() local
199 debug->debugfs_dir = debugfs_create_dir(dev_name(rkisp1->dev), NULL); in rkisp1_debug_init()
201 debugfs_create_ulong("data_loss", 0444, debug->debugfs_dir, in rkisp1_debug_init()
202 &debug->data_loss); in rkisp1_debug_init()
203 debugfs_create_ulong("outform_size_err", 0444, debug->debugfs_dir, in rkisp1_debug_init()
204 &debug->outform_size_error); in rkisp1_debug_init()
206 debug->debugfs_dir, in rkisp1_debug_init()
207 &debug->img_stabilization_size_error); in rkisp1_debug_init()
208 debugfs_create_ulong("inform_size_error", 0444, debug->debugfs_dir, in rkisp1_debug_init()
209 &debug->inform_size_error); in rkisp1_debug_init()
[all …]
/linux/Documentation/devicetree/bindings/arm/
H A Darm,coresight-cpu-debug.yaml4 $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 …]
/linux/drivers/staging/vc04_services/interface/
H A DTESTING86 Command: cat /sys/kernel/debug/vchiq/state
97 DEBUG: SLOT_HANDLER_COUNT = 20(0x14)
98 DEBUG: SLOT_HANDLER_LINE = 1937(0x791)
99 DEBUG: PARSE_LINE = 1864(0x748)
100 DEBUG: PARSE_HEADER = -249155224(0xf1263168)
101 DEBUG: PARSE_MSGID = 67362817(0x403e001)
102 DEBUG: AWAIT_COMPLETION_LINE = 0(0x0)
103 DEBUG: DEQUEUE_MESSAGE_LINE = 0(0x0)
104 DEBUG: SERVICE_CALLBACK_LINE = 0(0x0)
105 DEBUG: MSG_QUEUE_FULL_COUNT = 0(0x0)
[all …]
/linux/drivers/net/wireless/ath/ath9k/
H A Ddebug.c32 sc->debug.stats.istats.sync_cause_all++; in ath9k_debug_sync_cause()
34 sc->debug.stats.istats.sync_rtc_irq++; in ath9k_debug_sync_cause()
36 sc->debug.stats.istats.sync_mac_irq++; in ath9k_debug_sync_cause()
38 sc->debug.stats.istats.eeprom_illegal_access++; in ath9k_debug_sync_cause()
40 sc->debug.stats.istats.apb_timeout++; in ath9k_debug_sync_cause()
42 sc->debug.stats.istats.pci_mode_conflict++; in ath9k_debug_sync_cause()
44 sc->debug.stats.istats.host1_fatal++; in ath9k_debug_sync_cause()
46 sc->debug.stats.istats.host1_perr++; in ath9k_debug_sync_cause()
48 sc->debug.stats.istats.trcv_fifo_perr++; in ath9k_debug_sync_cause()
50 sc->debug.stats.istats.radm_cpl_ep++; in ath9k_debug_sync_cause()
[all …]
/linux/Documentation/gpu/amdgpu/display/
H A Ddc-debug.rst2 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 …]
/linux/drivers/pci/hotplug/
H A Dibmphp_ebda.c114 debug("%s - slot_min = %x\n", __func__, ptr->slot_min); in print_bus_info()
115 debug("%s - slot_max = %x\n", __func__, ptr->slot_max); in print_bus_info()
116 debug("%s - slot_count = %x\n", __func__, ptr->slot_count); in print_bus_info()
117 debug("%s - bus# = %x\n", __func__, ptr->busno); in print_bus_info()
118 debug("%s - current_speed = %x\n", __func__, ptr->current_speed); in print_bus_info()
119 debug("%s - controller_id = %x\n", __func__, ptr->controller_id); in print_bus_info()
121 debug("%s - slots_at_33_conv = %x\n", __func__, ptr->slots_at_33_conv); in print_bus_info()
122 debug("%s - slots_at_66_conv = %x\n", __func__, ptr->slots_at_66_conv); in print_bus_info()
123 debug("%s - slots_at_66_pcix = %x\n", __func__, ptr->slots_at_66_pcix); in print_bus_info()
124 debug("%s - slots_at_100_pcix = %x\n", __func__, ptr->slots_at_100_pcix); in print_bus_info()
[all …]
/linux/drivers/net/wireless/st/cw1200/
H A Ddebug.h35 ++priv->debug->tx; in cw1200_debug_txed()
40 ++priv->debug->tx_agg; in cw1200_debug_txed_agg()
46 ++priv->debug->tx_multi; in cw1200_debug_txed_multi()
47 priv->debug->tx_multi_frames += count; in cw1200_debug_txed_multi()
52 ++priv->debug->rx; in cw1200_debug_rxed()
57 ++priv->debug->rx_agg; in cw1200_debug_rxed_agg()
62 ++priv->debug->tx_cache_miss; in cw1200_debug_tx_cache_miss()
67 ++priv->debug->tx_align; in cw1200_debug_tx_align()
72 ++priv->debug->tx_ttl; in cw1200_debug_tx_ttl()
77 ++priv->debug->tx_burst; in cw1200_debug_tx_burst()
[all …]
/linux/Documentation/devicetree/bindings/soc/socionext/
H A Dsocionext,uniphier-soc-glue-debug.yaml4 $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 …]
/linux/Documentation/admin-guide/
H A Dbtmrvl.rst10 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 …]
/linux/arch/arm64/kvm/
H A Ddebug.c3 * Debug and Guest Debug support
12 #include <asm/debug-monitors.h>
29 * For some debug operations we need to tweak some guest registers. As
69 * kvm_arm_init_debug - grab what we need for debug
90 * - Debug ROM Address (MDCR_EL2_TDRA)
112 /* Route all software debug exceptions to EL2 */ in kvm_arm_setup_mdcr_el2()
116 * Trap debug register access when one of the following is true: in kvm_arm_setup_mdcr_el2()
117 * - Userspace is using the hardware to debug the guest in kvm_arm_setup_mdcr_el2()
119 * - The guest is not using debug (DEBUG_DIRTY clear). in kvm_arm_setup_mdcr_el2()
120 * - The guest has enabled the OS Lock (debug exceptions are blocked). in kvm_arm_setup_mdcr_el2()
[all …]
/linux/fs/orangefs/
H A Dorangefs-debugfs.c3 * What: /sys/kernel/debug/orangefs/debug-help
7 * List of client and kernel debug keywords.
10 * What: /sys/kernel/debug/orangefs/client-debug
14 * Debug setting for "the client", the userspace
18 * What: /sys/kernel/debug/orangefs/kernel-debug
22 * Debug setting for the orangefs kernel module.
25 * of keywords, from debug-help can be catted to
26 * client-debug or kernel-debug.
29 * for client-debug. Setting client-debug to "all"
35 * "none" and "all" are similar settings for kernel-debug
[all …]

12345678910>>...157