Home
last modified time | relevance | path

Searched refs:tracing (Results 1 – 25 of 231) sorted by relevance

12345678910

/OK3568_Linux_fs/kernel/Documentation/trace/
H A Dboottime-trace.rst4 Boot-time tracing
12 Boot-time tracing allows users to trace boot-time process including
17 this uses bootconfig file to describe tracing feature programming.
22 Here is the list of available options list for boot time tracing in
44 Stop tracing if WARN_ON() occurs.
50 Add fgraph tracing function filters.
53 Add fgraph non-tracing function filters.
65 Enable/Disable tracing on this instance when starting boot-time tracing.
88 This will take an array of tracing function filter rules.
91 This will take an array of NON-tracing function filter rules.
[all …]
H A Dmmiotrace.rst2 In-kernel memory-mapped I/O tracing
10 MMIO tracing was originally developed by Intel around 2003 for their Fault
12 Jeff Muizelaar created a tool for tracing MMIO accesses with the Nouveau
28 supported, but tracing is unreliable and may miss events if more than one CPU
39 $ echo mmiotrace > /sys/kernel/debug/tracing/current_tracer
40 $ cat /sys/kernel/debug/tracing/trace_pipe > mydump.txt &
42 $ echo "X is up" > /sys/kernel/debug/tracing/trace_marker
43 $ echo nop > /sys/kernel/debug/tracing/current_tracer
59 $ echo mmiotrace > /sys/kernel/debug/tracing/current_tracer
63 $ cat /sys/kernel/debug/tracing/trace_pipe > mydump.txt &
[all …]
H A Duprobetracer.rst15 /sys/kernel/debug/tracing/uprobe_events, and enable it via
16 /sys/kernel/debug/tracing/events/uprobes/<EVENT>/enable.
21 You can also use /sys/kernel/debug/tracing/dynamic_events instead of
82 /sys/kernel/debug/tracing/uprobe_profile. The first column is the filename,
90 echo 'p /bin/bash:0x4245c0' > /sys/kernel/debug/tracing/uprobe_events
94 echo 'r /bin/bash:0x4245c0' > /sys/kernel/debug/tracing/uprobe_events
98 echo '-:p_bash_0x4245c0' >> /sys/kernel/debug/tracing/uprobe_events
102 cat /sys/kernel/debug/tracing/uprobe_events
106 echo > /sys/kernel/debug/tracing/uprobe_events
111 # cd /sys/kernel/debug/tracing/
[all …]
H A Devents.rst13 using the event tracing infrastructure.
15 Not all tracepoints can be traced using the event tracing system;
17 tracing information is saved into the tracing buffer, and how the
18 tracing information should be printed.
26 The events which are available for tracing can be found in the file
27 /sys/kernel/debug/tracing/available_events.
30 to /sys/kernel/debug/tracing/set_event. For example::
32 # echo sched_wakeup >> /sys/kernel/debug/tracing/set_event
39 # echo '!sched_wakeup' >> /sys/kernel/debug/tracing/set_event
43 # echo > /sys/kernel/debug/tracing/set_event
[all …]
H A Dhwlat_detector.rst38 Write the ASCII text "hwlat" into the current_tracer file of the tracing system
39 (mounted at /sys/kernel/tracing or /sys/kernel/tracing). It is possible to
45 # echo hwlat > /sys/kernel/tracing/current_tracer
46 # echo 100 > /sys/kernel/tracing/tracing_thresh
48 The /sys/kernel/tracing/hwlat_detector interface contains the following files:
58 observed then the data will be written to the tracing ring buffer.
70 The following tracing directory files are used by the hwlat_detector:
72 in /sys/kernel/tracing:
H A Dkprobetrace.rst20 /sys/kernel/debug/tracing/kprobe_events, and enable it via
21 /sys/kernel/debug/tracing/events/kprobes/<EVENT>/enable.
23 You can also use /sys/kernel/debug/tracing/dynamic_events instead of
127 under tracing/events/kprobes/<EVENT>, at the directory you can see 'id',
149 /sys/kernel/debug/tracing/kprobe_profile.
173 …_sys_open dfd=%ax filename=%dx flags=%cx mode=+4($stack)' > /sys/kernel/debug/tracing/kprobe_events
183 echo 'r:myretprobe do_sys_open $retval' >> /sys/kernel/debug/tracing/kprobe_events
188 /sys/kernel/debug/tracing/events/kprobes/<EVENT>/format.
191 cat /sys/kernel/debug/tracing/events/kprobes/myprobe/format
214 echo > /sys/kernel/debug/tracing/kprobe_events
[all …]
H A Dhistogram.rst94 tracing code. Trying to apply that comm value to other pid
102 /sys/kernel/debug/tracing/events/net/netif_rx/trigger
104 # cat /sys/kernel/debug/tracing/events/net/netif_rx/hist
107 /sys/kernel/debug/tracing/events/net/netif_rx/trigger
152 Instead of enabling or disabling the tracing of the target event
163 /sys/kernel/debug/tracing/events/net/netif_receive_skb/trigger
166 /sys/kernel/debug/tracing/events/sched/sched_process_exec/trigger
169 /sys/kernel/debug/tracing/events/sched/sched_process_exit/trigger
202 tracing/error_log file. See Error Conditions in
212 # cat /sys/kernel/debug/tracing/events/kmem/kmalloc/format
[all …]
H A Devents-msr.rst5 The x86 kernel supports tracing most MSR (Model Specific Register) accesses.
11 /sys/kernel/debug/tracing/events/msr/
37 cat /sys/kernel/debug/tracing/trace | decode_msr.py /usr/src/linux/include/asm/msr-index.h
H A Dftrace.rst27 is really a framework of several assorted tracing utilities.
28 There's latency tracing to examine what occurs between interrupts
32 One of the most common uses of ftrace is the event tracing.
53 option will do) the directory /sys/kernel/tracing will be created. To mount
56 tracefs /sys/kernel/tracing tracefs defaults 0 0
60 mount -t tracefs nodev /sys/kernel/tracing
65 ln -s /sys/kernel/tracing /tracing
69 Before 4.1, all ftrace tracing control files were within the debugfs
70 file system, which is typically located at /sys/kernel/debug/tracing.
74 /sys/kernel/debug/tracing
[all …]
H A Devents-nmi.rst7 /sys/kernel/debug/tracing/events/nmi
34 cd /sys/kernel/debug/tracing/events/nmi/nmi_handler
40 $ cat /sys/kernel/debug/tracing/trace_pipe
/OK3568_Linux_fs/kernel/Documentation/core-api/irq/
H A Dirqflags-tracing.rst2 IRQ-flags state tracing
7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in
21 state changes. But an architecture can be irq-flags-tracing enabled in a
30 irq-flags-tracing support:
37 irq-flags-tracing is spent in this state: look at the lockdep
40 lockdep complaint in the irq-flags-tracing functions arch support is
43 excluded from the irq-tracing [and lock validation] mechanism via
46 In general there is no risk from having an incomplete irq-flags-tracing
49 should be no crashes due to irq-tracing bugs. (except if the assembly
/OK3568_Linux_fs/kernel/tools/lib/traceevent/Documentation/
H A Dlibtraceevent-cpus.txt6 tep_get_cpus, tep_set_cpus - Get / set the number of CPUs, which have a tracing
21 The _tep_get_cpus()_ function gets the number of CPUs, which have a tracing
24 The _tep_set_cpus()_ function sets the number of CPUs, which have a tracing
26 The _cpu_ argument is the number of CPUs with tracing data.
30 The _tep_get_cpus()_ functions returns the number of CPUs, which have tracing
43 printf("We have tracing data for %d CPUs", tep_get_cpus(tep));
/OK3568_Linux_fs/kernel/Documentation/firmware-guide/acpi/
H A Dmethod-tracing.rst15 method tracing facility.
20 ACPICA provides method tracing capability. And two functions are
80 There are special log entries added by the method tracing facility at
153 Note that all above method tracing facility related module parameters can
163 All method tracing functions can be configured via ACPI module
173 The temporary debug_layer used when the tracing feature is enabled.
179 The temporary debug_level used when the tracing feature is enabled.
185 The status of the tracing feature.
187 Users can enable/disable this debug tracing feature by executing
195 Disable the method tracing feature.
[all …]
/OK3568_Linux_fs/u-boot/doc/
H A DREADME.trace10 U-Boot supports a simple tracing feature which allows a record of excecution
33 way of trying out tracing before you use it on your actual board. To do
45 Build sandbox U-Boot with tracing enabled:
122 used after relocation, as a place to put function tracing
127 Define this to start tracing early, before relocation.
161 effect. Once you have done your optimisations, turn off tracing before
164 The best time to start tracing is right at the beginning of U-Boot. The
165 best time to stop tracing is right at the end. In practice it is hard
168 This implementation enables tracing early in board_init_f(). This means
197 Display tracing statistics
[all …]
/OK3568_Linux_fs/kernel/drivers/char/mwave/
H A DREADME8 0x0001 mwavedd api tracing
9 0x0002 smapi api tracing
10 0x0004 3780i tracing
11 0x0008 tp3780i tracing
/OK3568_Linux_fs/kernel/kernel/trace/
H A DKconfig87 Adds a very slight overhead to tracing when enabled.
90 bool "Register read/write tracing"
109 Provides an option to not automount tracefs in /sys/kernel/debug/tracing.
134 # be able to offer generic tracing facilities:
148 Enable the kernel tracing infrastructure.
158 kernel cmdline at boot time for debugging (tracing) driver
175 tracing is enabled by the administrator. If it's runtime disabled
194 bool "enable/disable function tracing dynamically"
199 This option will modify all the calls to function tracing
208 See the files in /sys/kernel/debug/tracing:
[all …]
/OK3568_Linux_fs/buildroot/package/lttng-tools/
H A DConfig.in13 Userspace utilities for the LTTng 2.x tracing
17 and stop tracing sessions. Analysis of the trace can be done
25 If userspace tracing is desired, you need to enable
/OK3568_Linux_fs/kernel/tools/lib/api/fs/
H A Dtracing_path.c20 static void __tracing_path_set(const char *tracing, const char *mountpoint) in __tracing_path_set() argument
24 mountpoint, tracing); in __tracing_path_set()
26 mountpoint, tracing, "events"); in __tracing_path_set()
/OK3568_Linux_fs/buildroot/package/lttng-modules/
H A DConfig.in5 Linux kernel modules for the LTTng 2.x kernel tracing
24 * CONFIG_HAVE_SYSCALL_TRACEPOINTS: system call tracing
26 * CONFIG_EVENT_TRACING: needed to allow block layer tracing
/OK3568_Linux_fs/kernel/Documentation/networking/device_drivers/ethernet/mellanox/
H A Dmlx5.rst284 For the list of support mlx5 events check /sys/kernel/debug/tracing/events/mlx5/
290 $ echo mlx5:mlx5e_configure_flower >> /sys/kernel/debug/tracing/set_event
291 $ cat /sys/kernel/debug/tracing/trace
297 $ echo mlx5:mlx5e_delete_flower >> /sys/kernel/debug/tracing/set_event
298 $ cat /sys/kernel/debug/tracing/trace
304 $ echo mlx5:mlx5e_stats_flower >> /sys/kernel/debug/tracing/set_event
305 $ cat /sys/kernel/debug/tracing/trace
311 $ echo mlx5:mlx5e_tc_update_neigh_used_value >> /sys/kernel/debug/tracing/set_event
312 $ cat /sys/kernel/debug/tracing/trace
318 $ echo mlx5:mlx5e_rep_neigh_update >> /sys/kernel/debug/tracing/set_event
[all …]
/OK3568_Linux_fs/kernel/Documentation/ABI/testing/
H A Dsysfs-bus-coresight-devices-etm4x5 Description: (RW) Enable/disable tracing on this specific trace entiry.
15 Description: (Read) The CPU this tracing entity is associated with.
22 available for tracing.
29 available for tracing.
36 tracing.
49 available for tracing.
56 for tracing.
70 available for tracing.
77 are available for tracing.
91 P0 instruction tracing, branch broadcast, cycle counting and
[all …]
/OK3568_Linux_fs/buildroot/package/gstreamer1/gstreamer1/
H A DConfig.in32 bool "enable tracing subsystem"
35 Enable the tracing subsystem within gstreamer. This may
42 Enable support for the gst-debug tracing functionality in
/OK3568_Linux_fs/kernel/drivers/oprofile/
H A Dcpu_buffer.c81 b->tracing = 0; in alloc_cpu_buffers()
289 cpu_buf->tracing = 1; in oprofile_begin_trace()
294 cpu_buf->tracing = 0; in oprofile_end_trace()
425 if (!cpu_buf->tracing) in oprofile_add_trace()
440 cpu_buf->tracing = 0; in oprofile_add_trace()
/OK3568_Linux_fs/buildroot/package/lttng-libust/
H A DConfig.in12 Userspace tracing library for the LTTng 2.x tracing
/OK3568_Linux_fs/yocto/poky/meta/recipes-kernel/lttng/
H A Dlttng-platforms.inc2 # Whether the platform supports kernel tracing
11 # Whether the platform supports userspace tracing

12345678910