Home
last modified time | relevance | path

Searched full:traces (Results 1 – 25 of 190) sorted by relevance

12345678

/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/lib/zstd/common/
H A Ddebug.h25 * Starting level 2, traces can be generated and pushed to stderr.
26 * The higher the level, the more verbose the traces.
61 * It's generally inconvenient to output traces > 5.
H A Ddebug.c19 * which can be used to dynamically influence the verbosity of traces,
/linux/tools/testing/selftests/ftrace/test.d/ftrace/
H A Dfgraph-filter-stack.tc52 fail "No schedule traces found?"
68 fail "No schedule traces found?"
H A Dfgraph-multi.tc75 fail "No traces found with $TEST?"
92 fail "No traces found with all tracing?"
H A Dfgraph-filter.tc37 fail "No schedule traces found?"
/linux/include/linux/
H A Dstackdepot.h6 * later retrieve many potentially duplicated stack traces without wasting
9 * For example, KASAN needs to save allocation and free stack traces for each
10 * object. Storing two stack traces per object requires a lot of memory (e.g.
12 * stack traces often repeat, using stack depot allows to save about 100x space.
/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/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/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()
1884 info->x_traces = traces; in elantech_query_info()
[all …]
/linux/drivers/hid/
H A Dhid-elan.c265 * sy / sx: finger width / height expressed in traces, the total number in elan_usb_report_input()
266 * of traces can be queried by doing a HID_REQ_SET_REPORT in elan_usb_report_input()
268 * returned buf, buf[3]=no-x-traces, buf[4]=no-y-traces. in elan_usb_report_input()
/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/Documentation/dev-tools/
H A Dkasan.rst96 To include alloc and free stack traces of affected slab objects into reports,
97 enable ``CONFIG_STACKTRACE``. To include alloc and free stack traces of affected
124 traces collection (default: ``on``).
278 Generic KASAN also reports up to two auxiliary call stack traces. These stack
279 traces point to places in code that interacted with the object but that are not
/linux/drivers/block/null_blk/
H A Dtrace.c10 * Helper to use for all null_blk traces to extract disk name.
/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/Documentation/trace/
H A Dintel_th.rst96 # .. wait for traces to pile up ..
117 software traces to the Software Trace Hub (an stm class device). The
H A Dfunction-graph-fold.vim1 " Enable folding for ftrace function_graph traces.
/linux/drivers/isdn/capi/
H A DKconfig21 If you say Y here, the kernelcapi driver can make verbose traces
/linux/drivers/net/wireless/ti/wl18xx/
H A Dacx.c277 wl1271_debug(DEBUG_ACX, "acx dynamic fw traces config %d", in wl18xx_acx_dynamic_fw_traces()
291 wl1271_warning("acx config dynamic fw traces failed: %d", ret); in wl18xx_acx_dynamic_fw_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/trace/coresight/
H A Dcoresight-perf.rst124 are in tests/shell/coresight and will collect traces to ensure a
161 quality of traces.
H A Dcoresight-trbe.rst14 memory, CPU traces generated from a corresponding percpu tracing unit. This
/linux/arch/xtensa/
H A DKconfig.debug40 prints in stack traces.
/linux/Documentation/hwmon/
H A Dmax31730.rst25 for high series resistance in circuit-board traces and the external thermal

12345678