Home
last modified time | relevance | path

Searched refs:traces (Results 1 – 25 of 112) sorted by relevance

12345

/OK3568_Linux_fs/yocto/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.4.bb2 …host side, as well as a trace converter, which used to convert LTTng 2.0 traces into human-readabl…
53 install -d "${D}${PTEST_PATH}/tests/data/ctf-traces/"
54 cp -a ${S}/tests/data/ctf-traces/* ${D}${PTEST_PATH}/tests/data/ctf-traces/
/OK3568_Linux_fs/kernel/kernel/trace/
H A DMakefile84 obj-$(CONFIG_TRACEPOINTS) += error_report-traces.o
85 obj-$(CONFIG_TRACEPOINTS) += power-traces.o
87 obj-$(CONFIG_TRACEPOINTS) += rpm-traces.o
/OK3568_Linux_fs/buildroot/package/babeltrace2/
H A DConfig.in.host9 analyze traces.
15 can read and write CTF traces.
H A DConfig.in13 analyze traces.
19 can read and write CTF traces.
/OK3568_Linux_fs/buildroot/package/trace-cmd/
H A DConfig.in10 kernel configuration. This command collect traces on your
11 target. You can analyse these traces on the target or on
/OK3568_Linux_fs/buildroot/board/qemu/arm-vexpress-tz/
H A Dreadme.txt22 The boot stage traces (if any) followed by the login prompt will appear
41 Enable TF-A traces from LOG_LEVEL (I.e LOG_LEVEL=40) from
48 their traces.
50 The ARM Trusted Firmware outputs its traces on the QEMU standard (first)
55 To get the OP-TEE OS traces, append a second -serial argument after
/OK3568_Linux_fs/yocto/poky/meta/recipes-devtools/gnu-config/gnu-config/
H A Dgnu-configize.in155 my $traces = new Autom4te::XFile
165 while ($_ = $traces->getline)
/OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-devtools/heaptrack/
H A Dheaptrack_1.2.0.bb2 DESCRIPTION = "Heaptrack traces all memory allocations and annotates these \
3 events with stack traces. Dedicated analysis tools then allow you to interpret \
/OK3568_Linux_fs/kernel/drivers/input/mouse/
H A Delantech.c678 int pres, traces; in process_packet_head_v4() local
686 traces = (packet[0] & 0xf0) >> 4; in process_packet_head_v4()
694 input_report_abs(dev, ABS_MT_TOUCH_MAJOR, traces * etd->width); in process_packet_head_v4()
696 input_report_abs(dev, ABS_TOOL_WIDTH, traces); in process_packet_head_v4()
1681 unsigned char traces; in elantech_query_info() local
1845 traces = info->capabilities[1]; in elantech_query_info()
1846 if ((traces < 2) || (traces > info->x_max)) in elantech_query_info()
1849 info->width = info->x_max / (traces - 1); in elantech_query_info()
1852 info->x_traces = traces; in elantech_query_info()
1855 traces = info->capabilities[2]; in elantech_query_info()
[all …]
/OK3568_Linux_fs/kernel/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
941 traces = (val >> 16) & 0xff; /* Number of Traces */ in genwqe_ffdc_buff_read()
947 for (trace = 0; trace <= traces; trace++) { in genwqe_ffdc_buff_read()
/OK3568_Linux_fs/kernel/drivers/md/persistent-data/
H A Ddm-block-manager.c50 struct stack_store traces[MAX_HOLDERS]; member
85 t = lock->traces + h; in __add_holder()
107 stack_trace_print(lock->traces[i].entries, in __check_holder()
108 lock->traces[i].nr_entries, 4); in __check_holder()
/OK3568_Linux_fs/buildroot/package/python-aiohttp/
H A D0001-Bump-async-timeout-version-for-aiohttp-3.8-5299.patch43 req, traces=traces, timeout=real_timeout
98 self, req: "ClientRequest", traces: List["Trace"], timeout: "ClientTimeout"
107 self, req: "ClientRequest", traces: List["Trace"], timeout: "ClientTimeout"
/OK3568_Linux_fs/kernel/tools/objtool/Documentation/
H A Dstack-validation.txt12 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
/OK3568_Linux_fs/buildroot/package/neard/
H A Dneard.mk14 NEARD_CONF_OPTS = --disable-traces
/OK3568_Linux_fs/buildroot/package/lttng-babeltrace/
H A DConfig.in.host11 can decode and display LTTng traces, since the latter are
H A DConfig.in18 can decode and display LTTng traces, since the latter are
/OK3568_Linux_fs/buildroot/package/apitrace/
H A DConfig.in20 inspect generated traces.
/OK3568_Linux_fs/external/rknpu2/examples/rknn_yolov5_android_apk_demo/app/
H A Dproguard-rules.pro16 # debugging stack traces.
/OK3568_Linux_fs/kernel/arch/x86/
H A DKconfig.debug240 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
/OK3568_Linux_fs/kernel/drivers/iommu/
H A DMakefile4 obj-$(CONFIG_IOMMU_API) += iommu-traces.o
/OK3568_Linux_fs/kernel/Documentation/trace/coresight/
H A Dcoresight-trbe.rst14 memory, CPU traces generated from a corresponding percpu tracing unit. This
/OK3568_Linux_fs/kernel/net/core/
H A DMakefile23 obj-$(CONFIG_TRACEPOINTS) += net-traces.o
/OK3568_Linux_fs/kernel/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
/OK3568_Linux_fs/kernel/Documentation/hwmon/
H A Dmax31730.rst25 for high series resistance in circuit-board traces and the external thermal

12345