| /kernel/linux/linux-5.10/include/linux/ |
| D | trace.h | 13 * can process traces and export them to a registered destination as
16 * If you want traces to be sent to some other place rather than ring
18 * its own .write() function for writing traces to the storage.
21 * write - copy traces which have been delt with ->commit() to
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-6.6/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.
14 * Stack traces are never removed from the stack depot.
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
299 If you're 100% sure the code won't affect stack traces, or if you're
440 that it won't affect kernel stack traces, you can tell objtool to
|
| /kernel/linux/linux-6.6/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.
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/tools/testing/selftests/ftrace/test.d/ftrace/ |
| D | fgraph-filter-stack.tc | 52 fail "No schedule traces found?"
68 fail "No schedule traces found?"
|
| /kernel/linux/linux-6.6/tools/testing/selftests/ftrace/test.d/ftrace/ |
| D | fgraph-filter-stack.tc | 52 fail "No schedule traces found?"
68 fail "No schedule traces found?"
|
| /kernel/linux/linux-6.6/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
254 stack traces.
266 traces. It scans the stack and reports every kernel text address it
|
| /kernel/linux/linux-5.10/arch/x86/ |
| D | Kconfig.debug | 240 traces for panics, oopses, bugs, warnings, perf, /proc/<pid>/stack,
249 unwinding kernel stack traces. It uses a custom data format which is
264 stack traces.
276 traces. It scans the stack and reports every kernel text address it
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/linux-5.10/kernel/trace/ |
| D | Makefile | 84 obj-$(CONFIG_TRACEPOINTS) += power-traces.o
86 obj-$(CONFIG_TRACEPOINTS) += rpm-traces.o
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/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()
1682 unsigned char traces; in elantech_query_info() local
1846 traces = info->capabilities[1]; in elantech_query_info()
1847 if ((traces < 2) || (traces > info->x_max)) in elantech_query_info()
1850 info->width = info->x_max / (traces - 1); in elantech_query_info()
1852 /* column number of traces */ in elantech_query_info()
1853 info->x_traces = traces; in elantech_query_info()
[all …]
|
| /kernel/linux/linux-6.6/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()
1682 unsigned char traces; in elantech_query_info() local
1846 traces = info->capabilities[1]; in elantech_query_info()
1847 if ((traces < 2) || (traces > info->x_max)) in elantech_query_info()
1850 info->width = info->x_max / (traces - 1); in elantech_query_info()
1852 /* column number of traces */ in elantech_query_info()
1853 info->x_traces = traces; in elantech_query_info()
[all …]
|
| /kernel/linux/linux-5.10/lib/ |
| D | stackdepot.c | 3 * Generic stack depot for storing stack traces.
5 * Some debugging tools need to save stack traces of certain events which can
7 * free stacks for each object, but storing two stack traces per object
|
| /kernel/linux/linux-5.10/drivers/block/null_blk/ |
| D | trace.c | 10 * Helper to use for all null_blk traces to extract disk name.
|
| /kernel/linux/linux-6.6/drivers/block/null_blk/ |
| D | trace.c | 10 * Helper to use for all null_blk traces to extract disk name.
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-6.6/lib/ |
| D | stackdepot.c | 6 * stack traces themselves are stored contiguously one after another in a set
78 /* Hash table of pointers to stored stack traces. */
85 /* Array of memory regions that store stack traces. */
136 * stack traces being stored in stack depot. in stack_depot_early_init()
|