Home
last modified time | relevance | path

Searched refs:traces (Results 1 – 25 of 73) sorted by relevance

123

/linux-6.1.9/arch/loongarch/
DKconfig.debug6 traces for panics, oopses, bugs, warnings, perf, /proc/<pid>/stack,
13 traces. It scans the stack and reports every kernel text address it
24 traces. It unwind the stack frame based on prologue code analyze. Symbol
/linux-6.1.9/kernel/trace/
DMakefile92 obj-$(CONFIG_TRACEPOINTS) += error_report-traces.o
93 obj-$(CONFIG_TRACEPOINTS) += power-traces.o
95 obj-$(CONFIG_TRACEPOINTS) += rpm-traces.o
/linux-6.1.9/drivers/input/mouse/
Delantech.c678 int pres, traces; in process_packet_head_v4() local
686 traces = (packet[0] & 0xf0) >> 4; in process_packet_head_v4()
694 input_report_abs(dev, ABS_MT_TOUCH_MAJOR, traces * etd->width); in process_packet_head_v4()
696 input_report_abs(dev, ABS_TOOL_WIDTH, traces); in process_packet_head_v4()
1681 unsigned char traces; in elantech_query_info() local
1845 traces = info->capabilities[1]; in elantech_query_info()
1846 if ((traces < 2) || (traces > info->x_max)) in elantech_query_info()
1849 info->width = info->x_max / (traces - 1); in elantech_query_info()
1852 info->x_traces = traces; in elantech_query_info()
1855 traces = info->capabilities[2]; in elantech_query_info()
[all …]
/linux-6.1.9/drivers/md/persistent-data/
Ddm-block-manager.c50 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-6.1.9/drivers/misc/genwqe/
Dcard_utils.c832 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-6.1.9/arch/arm64/boot/dts/freescale/
Dimx8mp-verdin-dev.dtsi43 /* Limit frequency on dev board due to long traces and bad signal integrity */
Dimx8mm-verdin-dev.dtsi65 /* Limit frequency on dev board due to long traces and bad signal integrity */
/linux-6.1.9/tools/objtool/Documentation/
Dobjtool.txt19 stack traces are reliable for live patching
100 code and C inline assembly code so that stack traces can be reliable.
113 a) More reliable stack traces for frame pointer enabled kernels
131 For stack traces based on frame pointers to be reliable, all
190 stack traces need to be reliable (or an unreliable condition needs to
219 This rule ensures that frame pointer based stack traces will work as
294 If you're 100% sure the code won't affect stack traces, or if you're
422 that it won't affect kernel stack traces, you can tell objtool to
/linux-6.1.9/Documentation/trace/coresight/
Dcoresight-trbe.rst14 memory, CPU traces generated from a corresponding percpu tracing unit. This
Dcoresight-perf.rst93 are in tests/shell/coresight and will collect traces to ensure a
130 quality of traces.
/linux-6.1.9/Documentation/hwmon/
Dmax31730.rst25 for high series resistance in circuit-board traces and the external thermal
/linux-6.1.9/net/core/
DMakefile25 obj-$(CONFIG_TRACEPOINTS) += net-traces.o
/linux-6.1.9/drivers/iommu/
DMakefile4 obj-$(CONFIG_IOMMU_API) += iommu-traces.o
/linux-6.1.9/arch/x86/
DKconfig.debug230 traces for panics, oopses, bugs, warnings, perf, /proc/<pid>/stack,
239 unwinding kernel stack traces. It uses a custom data format which is
254 stack traces.
266 traces. It scans the stack and reports every kernel text address it
/linux-6.1.9/Documentation/trace/
Dfunction-graph-fold.vim1 " Enable folding for ftrace function_graph traces.
Dintel_th.rst96 # .. wait for traces to pile up ..
117 software traces to the Software Trace Hub (an stm class device). The
/linux-6.1.9/arch/xtensa/
DKconfig.debug40 prints in stack traces.
/linux-6.1.9/drivers/isdn/capi/
DKconfig21 If you say Y here, the kernelcapi driver can make verbose traces
/linux-6.1.9/Documentation/admin-guide/kdump/
Dgdbmacros.txt3 # 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-6.1.9/Documentation/usb/
Dusbmon.rst9 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-6.1.9/Documentation/devicetree/bindings/arm/
Darm,coresight-etb10.yaml23 The CoreSight Embedded Trace Buffer stores traces in a dedicated SRAM that is
/linux-6.1.9/Documentation/filesystems/caching/
Dfscache.rst241 CACHE Cache cookie debug ID (also appears in traces)
271 VOLUME The volume cookie debug ID (also appears in traces)
307 COOKIE The cookie debug ID (also appears in traces)
/linux-6.1.9/Documentation/networking/device_drivers/atm/
Diphase.rst128 IADebugFlag, which controls the output of the traces. You can find the bit
132 traces together with loading the driver.
/linux-6.1.9/Documentation/core-api/irq/
Dirqflags-tracing.rst7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
/linux-6.1.9/drivers/hwtracing/intel_th/
DKconfig65 storing STP traces to system memory. It supports single

123