Home
last modified time | relevance | path

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

12345678910>>...12

/openbmc/openpower-proc-control/extensions/phal/
H A Dphal_error.hpp15 * @brief Process debug traces
17 * Function adds debug traces to the list so that it will be added to the
31 * If status is success log traces are cleared else used in the
41 * If status is success log traces are cleared else used in the
63 * boot. It collects the traces and create a PEL
75 * @brief Add callbacks for debug traces and boot errors
77 * This function adds callback for debug traces and for boot
/openbmc/docs/designs/
H A Derror-log-handling-for-phal.md117 error logging traces.
119 Debug traces returned through the callback method will be added to the PEL.
124 error logging traces.
126 Debug traces returned through the callback method will be added to the PEL.
130 Applications need to register callback methods to get the debug traces from
133 Debug traces returned through the callback method will be added to the PEL.
137 ### Register for debug traces and boot errors
141 ### Process debug traces
/openbmc/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
/openbmc/linux/include/linux/
H A Dtrace.h11 * 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
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.
14 * Stack traces are never removed from the stack depot.
/openbmc/openbmc/poky/meta/recipes-kernel/lttng/
H A Dbabeltrace_1.5.11.bb2 …host side, as well as a trace converter, which used to convert LTTng 2.0 traces into human-readabl…
53 install -d "$f" "${D}${PTEST_PATH}/tests/ctf-traces/"
54 cp -a ${S}/tests/ctf-traces/* ${D}${PTEST_PATH}/tests/ctf-traces/
H A Dbabeltrace2_2.0.6.bb2 …host side, as well as a trace converter, which used to convert LTTng 2.0 traces into human-readabl…
55 install -d "${D}${PTEST_PATH}/tests/data/ctf-traces/"
56 cp -a ${S}/tests/data/ctf-traces/* ${D}${PTEST_PATH}/tests/data/ctf-traces/
/openbmc/openbmc/poky/meta/recipes-graphics/mesa/files/
H A D0001-freedreno-don-t-encode-build-path-into-binaries.patch28 command: [asm, '-g', '6', files('../.gitlab-ci/traces/afuc_test.asm'), '@OUTPUT@'],
48 command: [cffdump, '--unit-test', args, files('../.gitlab-ci/traces/' + name + '.rd.gz')],
55 command: [crashdec, args, files('../.gitlab-ci/traces/' + name + '.devcore')],
/openbmc/linux/tools/objtool/Documentation/
H A Dobjtool.txt19 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
/openbmc/linux/lib/zstd/common/
H A Ddebug.h24 * 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.
/openbmc/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
/openbmc/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?"
/openbmc/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
/openbmc/openpower-hw-diags/attn/
H A Dattn_common.hpp44 * @brief Traces some regs for hostboot
48 * by tracing them and then the traces will get added to the error
/openbmc/qemu/include/hw/xen/interface/
H A Dtrace.h22 #define TRC_PV 0x0020f000 /* Xen PV traces */
24 #define TRC_HW 0x0080f000 /* Xen hardware-related traces */
25 #define TRC_GUEST 0x0800f000 /* Guest-generated traces */
76 #define TRC_HW_PM 0x00801000 /* Power management traces */
77 #define TRC_HW_IRQ 0x00802000 /* Traces relating to the handling of IRQs */
/openbmc/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()
/openbmc/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
/openbmc/phosphor-debug-collector/tools/dreport.d/plugins.d/
H A Dtraceevents9 desc="Kernel event traces"
/openbmc/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 …]
/openbmc/linux/lib/
H A Dstackdepot.c6 * 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()
/openbmc/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()
/openbmc/linux/drivers/block/null_blk/
H A Dtrace.c10 * Helper to use for all null_blk traces to extract disk name.
/openbmc/phosphor-host-ipmid/
H A DREADME.md28 ## Enable debug traces
/openbmc/qemu/docs/
H A Dqemu-option-trace.rst.inc24 Log output traces to *FILE*.
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Chassis/Buttons/
H A DNMI.interface.yaml3 is a non-maskable interrupt or signal for generating diagnostic traces and

12345678910>>...12