| /Linux-v5.15/kernel/trace/ |
| D | Makefile | 86 obj-$(CONFIG_TRACEPOINTS) += error_report-traces.o
87 obj-$(CONFIG_TRACEPOINTS) += power-traces.o
89 obj-$(CONFIG_TRACEPOINTS) += rpm-traces.o
|
| /Linux-v5.15/drivers/input/mouse/ |
| D | elantech.c | 665 int pres, traces; in process_packet_head_v4() local
673 traces = (packet[0] & 0xf0) >> 4; in process_packet_head_v4()
681 input_report_abs(dev, ABS_MT_TOUCH_MAJOR, traces * etd->width); in process_packet_head_v4()
683 input_report_abs(dev, ABS_TOOL_WIDTH, traces); in process_packet_head_v4()
1662 unsigned char traces; in elantech_query_info() local
1826 traces = info->capabilities[1]; in elantech_query_info()
1827 if ((traces < 2) || (traces > info->x_max)) in elantech_query_info()
1830 info->width = info->x_max / (traces - 1); in elantech_query_info()
1833 info->x_traces = traces; in elantech_query_info()
1836 traces = info->capabilities[2]; in elantech_query_info()
[all …]
|
| /Linux-v5.15/drivers/md/persistent-data/ |
| D | dm-block-manager.c | 50 struct stack_store traces[MAX_HOLDERS]; member
85 t = lock->traces + h; in __add_holder()
107 stack_trace_print(lock->traces[i].entries, in __check_holder()
108 lock->traces[i].nr_entries, 4); in __check_holder()
|
| /Linux-v5.15/drivers/misc/genwqe/ |
| D | card_utils.c | 832 int entries = 0, ring, traps, traces, trace_entries; in genwqe_ffdc_buff_size() local
872 traces = (val >> 16) & 0xff; in genwqe_ffdc_buff_size()
875 entries += traps + (traces * trace_entries); in genwqe_ffdc_buff_size()
890 int i, traps, traces, trace, trace_entries, trace_entry, ring; in genwqe_ffdc_buff_read() local
941 traces = (val >> 16) & 0xff; /* Number of Traces */ in genwqe_ffdc_buff_read()
947 for (trace = 0; trace <= traces; trace++) { in genwqe_ffdc_buff_read()
|
| /Linux-v5.15/tools/objtool/Documentation/ |
| D | stack-validation.txt | 12 that stack traces can be reliable.
33 a) More reliable stack traces for frame pointer enabled kernels
51 For stack traces based on frame pointers to be reliable, all
110 stack traces need to be reliable (or an unreliable condition needs to
142 This rule ensures that frame pointer based stack traces will work as
216 If you're 100% sure the code won't affect stack traces, or if you're
344 that it won't affect kernel stack traces, you can tell objtool to
|
| /Linux-v5.15/Documentation/trace/coresight/ |
| D | coresight-trbe.rst | 14 memory, CPU traces generated from a corresponding percpu tracing unit. This
|
| /Linux-v5.15/net/core/ |
| D | Makefile | 22 obj-$(CONFIG_TRACEPOINTS) += net-traces.o
|
| /Linux-v5.15/Documentation/hwmon/ |
| D | max31730.rst | 25 for high series resistance in circuit-board traces and the external thermal
|
| /Linux-v5.15/drivers/iommu/ |
| D | Makefile | 4 obj-$(CONFIG_IOMMU_API) += iommu-traces.o
|
| /Linux-v5.15/arch/x86/ |
| D | Kconfig.debug | 234 traces for panics, oopses, bugs, warnings, perf, /proc/<pid>/stack,
243 unwinding kernel stack traces. It uses a custom data format which is
258 stack traces.
270 traces. It scans the stack and reports every kernel text address it
|
| /Linux-v5.15/Documentation/trace/ |
| D | function-graph-fold.vim | 1 " Enable folding for ftrace function_graph traces.
|
| D | intel_th.rst | 96 # .. wait for traces to pile up ..
117 software traces to the Software Trace Hub (an stm class device). The
|
| /Linux-v5.15/arch/xtensa/ |
| D | Kconfig.debug | 40 prints in stack traces.
|
| /Linux-v5.15/drivers/isdn/capi/ |
| D | Kconfig | 21 If you say Y here, the kernelcapi driver can make verbose traces
|
| /Linux-v5.15/Documentation/admin-guide/kdump/ |
| D | gdbmacros.txt | 3 # useful information from kernel crashdump (kdump) like stack traces of
55 dump all thread stack traces on a kernel compiled with !CONFIG_FRAME_POINTER
101 dump all thread stack traces on a kernel compiled with CONFIG_FRAME_POINTER
|
| /Linux-v5.15/Documentation/usb/ |
| D | usbmon.rst | 9 used to collect traces of I/O on the USB bus. This function is analogous
12 USBMon (with uppercase letters) is used to examine raw traces produced
16 Controller Drivers (HCD). So, if HCD is buggy, the traces reported by
24 How to use usbmon to collect raw text traces
27 Unlike the packet socket, usbmon has an interface which provides traces
|
| /Linux-v5.15/Documentation/networking/device_drivers/atm/ |
| D | iphase.rst | 128 IADebugFlag, which controls the output of the traces. You can find the bit
132 traces together with loading the driver.
|
| /Linux-v5.15/Documentation/core-api/irq/ |
| D | irqflags-tracing.rst | 7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
|
| /Linux-v5.15/Documentation/dev-tools/ |
| D | kasan.rst | 56 To include alloc and free stack traces of affected slab objects into reports,
57 enable ``CONFIG_STACKTRACE``. To include alloc and free stack traces of affected
169 Generic KASAN also reports up to two auxiliary call stack traces. These stack
170 traces point to places in code that interacted with the object but that are not
207 traces collection (default: ``on``).
|
| /Linux-v5.15/drivers/hwtracing/intel_th/ |
| D | Kconfig | 65 storing STP traces to system memory. It supports single
|
| /Linux-v5.15/Documentation/RCU/ |
| D | stallwarn.rst | 112 To diagnose the cause of the stall, inspect the stack traces.
115 comparing the stack traces can often help determine where the stall
168 own warnings, as this often gives better-quality stack traces.
320 involved in the stall. These stack traces can help you locate the cause
|
| /Linux-v5.15/arch/arm/boot/dts/ |
| D | ls1021a-tsn.dts | 118 /* RGMII delays added via PCB traces */
|
| /Linux-v5.15/net/batman-adv/ |
| D | Kconfig | 93 say N here. Select this option to gather traces like the debug
|
| /Linux-v5.15/include/linux/ |
| D | remoteproc.h | 546 struct list_head traces; member
|
| /Linux-v5.15/arch/powerpc/ |
| D | Kconfig.debug | 24 prints in stack traces. This can be useful if your display is
25 too small and stack traces cause important information to
|
