| /Linux-v4.19/kernel/trace/ |
| D | Makefile | 74 obj-$(CONFIG_TRACEPOINTS) += power-traces.o
76 obj-$(CONFIG_TRACEPOINTS) += rpm-traces.o
|
| /Linux-v4.19/drivers/misc/genwqe/ |
| D | card_utils.c | 853 int entries = 0, ring, traps, traces, trace_entries; in genwqe_ffdc_buff_size() local
893 traces = (val >> 16) & 0xff; in genwqe_ffdc_buff_size()
896 entries += traps + (traces * trace_entries); in genwqe_ffdc_buff_size()
907 int i, traps, traces, trace, trace_entries, trace_entry, ring; in genwqe_ffdc_buff_read() local
958 traces = (val >> 16) & 0xff; /* Number of Traces */ in genwqe_ffdc_buff_read()
964 for (trace = 0; trace <= traces; trace++) { in genwqe_ffdc_buff_read()
|
| /Linux-v4.19/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
301 that it won't affect kernel stack traces, you can tell objtool to
|
| /Linux-v4.19/drivers/input/mouse/ |
| D | elantech.c | 581 int pres, traces; in process_packet_head_v4() local
589 traces = (packet[0] & 0xf0) >> 4; in process_packet_head_v4()
597 input_report_abs(dev, ABS_MT_TOUCH_MAJOR, traces * etd->width); in process_packet_head_v4()
599 input_report_abs(dev, ABS_TOOL_WIDTH, traces); in process_packet_head_v4()
1005 unsigned char traces; in elantech_set_range() local
1068 traces = info->capabilities[1]; in elantech_set_range()
1069 if ((traces < 2) || (traces > *x_max)) in elantech_set_range()
1072 *width = *x_max / (traces - 1); in elantech_set_range()
|
| /Linux-v4.19/net/core/ |
| D | Makefile | 22 obj-$(CONFIG_TRACEPOINTS) += net-traces.o
|
| /Linux-v4.19/Documentation/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-v4.19/drivers/md/persistent-data/ |
| D | dm-block-manager.c | 47 struct stack_trace traces[MAX_HOLDERS]; member
83 t = lock->traces + h; in __add_holder()
109 print_stack_trace(lock->traces + i, 4); in __check_holder()
|
| /Linux-v4.19/drivers/iommu/ |
| D | Makefile | 3 obj-$(CONFIG_IOMMU_API) += iommu-traces.o
|
| /Linux-v4.19/Documentation/trace/ |
| D | function-graph-fold.vim | 1 " Enable folding for ftrace function_graph traces.
|
| D | intel_th.rst | 93 # .. wait for traces to pile up ..
114 software traces to the Software Trace Hub (an stm class device). The
|
| /Linux-v4.19/drivers/isdn/capi/ |
| D | Kconfig | 5 If you say Y here, the kernelcapi driver can make verbose traces
|
| /Linux-v4.19/Documentation/usb/ |
| D | usbmon.txt | 4 used to collect traces of I/O on the USB bus. This function is analogous
7 USBMon (with uppercase letters) is used to examine raw traces produced
11 Controller Drivers (HCD). So, if HCD is buggy, the traces reported by
19 * How to use usbmon to collect raw text traces
21 Unlike the packet socket, usbmon has an interface which provides traces
|
| /Linux-v4.19/Documentation/networking/ |
| D | iphase.txt | 111 IADebugFlag, which controls the output of the traces. You can find the bit
115 traces together with loading the driver.
|
| /Linux-v4.19/arch/x86/ |
| D | Kconfig.debug | 358 traces for panics, oopses, bugs, warnings, perf, /proc/<pid>/stack,
367 unwinding kernel stack traces. It uses a custom data format which is
382 stack traces.
398 traces. It scans the stack and reports every kernel text address it
|
| /Linux-v4.19/Documentation/ |
| D | irqflags-tracing.txt | 7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
|
| /Linux-v4.19/include/linux/ |
| D | remoteproc.h | 456 struct list_head traces; member
|
| /Linux-v4.19/drivers/hwtracing/intel_th/ |
| D | Kconfig | 64 storing STP traces to system memory. It supports single
|
| /Linux-v4.19/fs/pstore/ |
| D | Kconfig | 133 With this option kernel traces function calls into a persistent
|
| /Linux-v4.19/drivers/remoteproc/ |
| D | remoteproc_core.c | 498 list_add_tail(&trace->node, &rproc->traces); in rproc_handle_trace()
875 list_for_each_entry_safe(entry, tmp, &rproc->traces, node) { in rproc_resource_cleanup()
1629 INIT_LIST_HEAD(&rproc->traces); in rproc_alloc()
|
| /Linux-v4.19/drivers/hwtracing/coresight/ |
| D | Kconfig | 53 connected to an external host for use case capturing more traces than
|
| /Linux-v4.19/Documentation/RCU/ |
| D | stallwarn.txt | 95 To diagnose the cause of the stall, inspect the stack traces.
98 comparing the stack traces can often help determine where the stall
147 own warnings, as this often gives better-quality stack traces.
|
| /Linux-v4.19/arch/powerpc/ |
| D | Kconfig.debug | 25 prints in stack traces. This can be useful if your display is
26 too small and stack traces cause important information to
|
| /Linux-v4.19/arch/arm/boot/dts/ |
| D | sun8i-a83t-allwinner-h8homlet-v2.dts | 229 * Set a 100ms delay to account for PMIC ramp time and board traces.
|
| D | sun8i-a83t-bananapi-m3.dts | 349 * ramp time and board traces.
|
| /Linux-v4.19/Documentation/sound/hd-audio/ |
| D | notes.rst | 628 ``hda:hda_send_cmd`` traces each CORB write while ``hda:hda_get_response``
629 traces the response from RIRB (only when read from the codec driver).
630 ``hda:hda_bus_reset`` traces the bus-reset due to fatal error, etc,
631 ``hda:hda_unsol_event`` traces the unsolicited events, and
640 then after some commands, you can traces from
|
