Home
last modified time | relevance | path

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

123

/linux/arch/loongarch/
H A 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
35 unwinding kernel stack traces. It uses a custom data format which is
/linux/kernel/trace/
H A DMakefile92 obj-$(CONFIG_TRACEPOINTS) += error_report-traces.o
93 obj-$(CONFIG_TRACEPOINTS) += power-traces.o
95 obj-$(CONFIG_TRACEPOINTS) += rpm-traces.o
/linux/drivers/input/mouse/
H A Delantech.c678 int pres, traces; in process_packet_head_v4() local
687 traces = (packet[0] & 0xf0) >> 4; in process_packet_head_v4()
695 input_report_abs(dev, ABS_MT_TOUCH_MAJOR, traces * etd->width); in process_packet_head_v4()
697 input_report_abs(dev, ABS_TOOL_WIDTH, traces); in process_packet_head_v4()
1713 unsigned char traces; in elantech_query_info() local
1877 traces = info->capabilities[1]; in elantech_query_info()
1878 if ((traces < 2) || (traces > info->x_max)) in elantech_query_info()
1881 info->width = info->x_max / (traces - 1); in elantech_query_info()
1883 /* column number of traces */ in elantech_query_info()
[all...]
/linux/Documentation/arch/powerpc/
H A Dhtm.rst55 To collect HTM traces for a partition represented by nodeindex as
93 This trace file will contain the relevant instruction traces
100 It is now possible to collect traces for a particular core/chip
/linux/drivers/md/persistent-data/
H A Ddm-block-manager.c51 struct stack_store traces[MAX_HOLDERS]; member
86 t = lock->traces + h; in __add_holder()
109 stack_trace_print(lock->traces[i].entries, in __check_holder()
110 lock->traces[i].nr_entries, 4); in __check_holder()
/linux/drivers/misc/genwqe/
H A 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
929 * To save time, there are only 6 traces poplulated on Uid=2, in genwqe_ffdc_buff_read()
941 traces = (val >> 16) & 0xff; /* Number of Traces */ in genwqe_ffdc_buff_read()
945 /* (for the trace == 0 case) as well as the traces 1 to */ in genwqe_ffdc_buff_read()
946 /* 'traces'. */ in genwqe_ffdc_buff_read()
947 for (trace = 0; trace <= traces; trace++) { in genwqe_ffdc_buff_read()
/linux/Documentation/trace/coresight/
H A Dcoresight-trbe.rst14 memory, CPU traces generated from a corresponding percpu tracing unit. This
H A Dcoresight-perf.rst124 are in tests/shell/coresight and will collect traces to ensure a
161 quality of traces.
/linux/Documentation/hwmon/
H A Dmax31730.rst25 for high series resistance in circuit-board traces and the external thermal
/linux/drivers/iommu/
H A DMakefile8 obj-$(CONFIG_IOMMU_API) += iommu-traces.o
/linux/arch/x86/
H A 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
255 stack traces.
267 traces. It scans the stack and reports every kernel text address it
/linux/tools/objtool/Documentation/
H A Dobjtool.txt19 stack traces are reliable for live patching
112 code and C inline assembly code so that stack traces can be reliable.
125 a) More reliable stack traces for frame pointer enabled kernels
143 For stack traces based on frame pointers to be reliable, all
202 stack traces need to be reliable (or an unreliable condition needs to
229 This rule ensures that frame pointer based stack traces will work as
330 traces and want objtool to ignore it, see "Adding exceptions" below.
468 that it won't affect kernel stack traces, you can tell objtool to
/linux/Documentation/trace/
H A Dfunction-graph-fold.vim1 " Enable folding for ftrace function_graph traces.
H A Dintel_th.rst96 # .. wait for traces to pile up ..
117 software traces to the Software Trace Hub (an stm class device). The
/linux/drivers/isdn/capi/
H A DKconfig21 If you say Y here, the kernelcapi driver can make verbose traces
/linux/net/core/
H A DMakefile28 obj-$(CONFIG_TRACEPOINTS) += net-traces.o
/linux/Documentation/admin-guide/kdump/
H A 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/arch/xtensa/
H A DKconfig.debug40 prints in stack traces.
/linux/Documentation/usb/
H A 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/arch/arm64/boot/dts/freescale/
H A Dimx8mm-verdin-dev.dtsi161 /* Limit frequency on dev board due to long traces and bad signal integrity */
H A Dimx8mp-verdin-dev.dtsi265 /* Limit frequency on dev board due to long traces and bad signal integrity */
/linux/Documentation/filesystems/caching/
H A 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/Documentation/networking/device_drivers/atm/
H A Diphase.rst128 IADebugFlag, which controls the output of the traces. You can find the bit
132 traces together with loading the driver.
/linux/Documentation/core-api/irq/
H A Dirqflags-tracing.rst7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
/linux/drivers/hwtracing/intel_th/
H A DKconfig66 storing STP traces to system memory. It supports single

123