| /linux-6.12.1/arch/loongarch/ |
| D | Kconfig.debug | 6 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-6.12.1/include/linux/ |
| D | trace.h | 11 * can process traces and export them to a registered destination as
14 * If you want traces to be sent to some other place rather than ring
16 * its own .write() function for writing traces to the storage.
19 * write - copy traces which have been delt with ->commit() to
|
| D | stackdepot.h | 6 * 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-6.12.1/lib/zstd/common/ |
| D | debug.h | 24 * Starting level 2, traces can be generated and pushed to stderr.
25 * The higher the level, the more verbose the traces.
61 * It's generally inconvenient to output traces > 5.
|
| D | debug.c | 18 * which can be used to dynamically influence the verbosity of traces,
|
| /linux-6.12.1/kernel/trace/ |
| D | Makefile | 92 obj-$(CONFIG_TRACEPOINTS) += error_report-traces.o
93 obj-$(CONFIG_TRACEPOINTS) += power-traces.o
95 obj-$(CONFIG_TRACEPOINTS) += rpm-traces.o
|
| /linux-6.12.1/tools/objtool/Documentation/ |
| D | objtool.txt | 19 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
318 If you're 100% sure the code won't affect stack traces, or if you're
459 that it won't affect kernel stack traces, you can tell objtool to
|
| /linux-6.12.1/arch/x86/ |
| D | Kconfig.debug | 230 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-6.12.1/tools/testing/selftests/ftrace/test.d/ftrace/ |
| D | fgraph-filter-stack.tc | 52 fail "No schedule traces found?"
68 fail "No schedule traces found?"
|
| D | fgraph-multi.tc | 75 fail "No traces found with $TEST?"
92 fail "No traces found with all tracing?"
|
| D | fgraph-filter.tc | 37 fail "No schedule traces found?"
|
| /linux-6.12.1/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
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-6.12.1/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-6.12.1/drivers/input/mouse/ |
| D | elantech.c | 678 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-6.12.1/drivers/hid/ |
| D | hid-elan.c | 265 * 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-6.12.1/drivers/block/null_blk/ |
| D | trace.c | 10 * Helper to use for all null_blk traces to extract disk name.
|
| /linux-6.12.1/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-6.12.1/Documentation/dev-tools/ |
| D | kasan.rst | 96 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``).
275 Generic KASAN also reports up to two auxiliary call stack traces. These stack
276 traces point to places in code that interacted with the object but that are not
|
| /linux-6.12.1/Documentation/trace/coresight/ |
| D | coresight-perf.rst | 93 are in tests/shell/coresight and will collect traces to ensure a
130 quality of traces.
|
| /linux-6.12.1/drivers/md/persistent-data/ |
| D | dm-block-manager.c | 51 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-6.12.1/drivers/isdn/capi/ |
| D | Kconfig | 21 If you say Y here, the kernelcapi driver can make verbose traces
|
| /linux-6.12.1/Documentation/trace/ |
| D | intel_th.rst | 96 # .. wait for traces to pile up ..
117 software traces to the Software Trace Hub (an stm class device). The
|
| D | function-graph-fold.vim | 1 " Enable folding for ftrace function_graph traces.
|
| /linux-6.12.1/arch/xtensa/ |
| D | Kconfig.debug | 40 prints in stack traces.
|
| /linux-6.12.1/drivers/net/wireless/ti/wl18xx/ |
| D | acx.c | 277 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()
|