| /linux/Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| H A D | tracepoints.rst | 13 For the list of support mlx5 events, check /sys/kernel/tracing/events/mlx5/.
19 $ echo mlx5:mlx5e_configure_flower >> /sys/kernel/tracing/set_event
20 $ cat /sys/kernel/tracing/trace
26 $ echo mlx5:mlx5e_delete_flower >> /sys/kernel/tracing/set_event
27 $ cat /sys/kernel/tracing/trace
33 $ echo mlx5:mlx5e_stats_flower >> /sys/kernel/tracing/set_event
34 $ cat /sys/kernel/tracing/trace
40 $ echo mlx5:mlx5e_tc_update_neigh_used_value >> /sys/kernel/tracing/set_event
41 $ cat /sys/kernel/tracing/trace
47 $ echo mlx5:mlx5e_rep_neigh_update >> /sys/kernel/tracing/set_event
[all …]
|
| /linux/tools/testing/selftests/ftrace/test.d/ftrace/ |
| H A D | func_traceonoff_triggers.tc | 10 # tracing, enabling or disabling trace events, or recording a stack trace
13 # This test is designed to test enabling and disabling tracing triggers
23 echo "Testing function probes with enabling disabling tracing:"
29 echo '** DISABLE TRACING'
43 echo '** ENABLE TRACING'
85 fail "Tracing is not stopped"
90 fail "Tracing is not off"
98 fail "Tracing file is still changing"
105 fail "Tracing is still happeing"
117 fail "Tracing is started again"
[all …]
|
| /linux/kernel/trace/ |
| H A D | Kconfig | 139 Adds a very slight overhead to tracing when enabled.
144 select TRACING
151 # enabled by all tracers (context switch and event tracer) they select TRACING.
154 # GENERIC_TRACER and TRACING to avoid circular dependencies to accomplish the
157 config TRACING config
170 select TRACING
174 # be able to offer generic tracing facilities:
187 Enable the kernel tracing infrastructure.
192 bool "Boot-time Tracing support"
193 depends on TRACING
[all...] |
| H A D | trace_selftest.c | 53 /* disable tracing */ in trace_test_buffer_cpu()
369 /* enable tracing, and record the filter function */ in trace_selftest_startup_dynamic_tracing()
385 /* enable tracing */ in trace_selftest_startup_dynamic_tracing()
412 /* stop the tracing. */ in trace_selftest_startup_dynamic_tracing()
430 /* Test the ops with global tracing running */ in trace_selftest_startup_dynamic_tracing()
437 /* Enable tracing on all functions again */ in trace_selftest_startup_dynamic_tracing()
440 /* Test the ops with global tracing off */ in trace_selftest_startup_dynamic_tracing()
473 * tracing utility. in trace_selftest_test_recursion_safe_func()
502 /* enable tracing, and record the filter function */ in trace_selftest_function_recursion()
618 /* enable tracing, and record the filter function */ in trace_selftest_function_regs()
[all …]
|
| /linux/Documentation/trace/ |
| H A D | mmiotrace.rst | 2 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
26 Mmiotrace feature is compiled in by the CONFIG_MMIOTRACE option. Tracing is
28 supported, but tracing is unreliable and may miss events if more than one CPU
39 $ echo mmiotrace > /sys/kernel/tracing/current_tracer
40 $ cat /sys/kernel/tracing/trace_pipe > mydump.txt &
42 $ echo "X is up" > /sys/kernel/tracing/trace_marker
43 $ echo nop > /sys/kernel/tracing/current_tracer
59 $ echo mmiotrace > /sys/kernel/tracing/current_tracer
[all …]
|
| H A D | boottime-trace.rst | 4 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 D | events.rst | 2 Event Tracing
13 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.
20 2. Using Event Tracing
26 The events which are available for tracing can be found in the file
27 /sys/kernel/tracing/available_events.
30 to /sys/kernel/tracing/set_event. For example::
32 # echo sched_wakeup >> /sys/kernel/tracing/set_event
[all …]
|
| H A D | timerlat-tracer.rst | 10 goal of timerlat is tracing in such a way to help kernel developers.
16 tracing system (generally mounted at /sys/kernel/tracing).
20 [root@f32 ~]# cd /sys/kernel/tracing/
21 [root@f32 tracing]# echo timerlat > current_tracer
25 [root@f32 tracing]# cat trace
71 - stop_tracing_us: stop the system tracing if a
74 - stop_tracing_total_us: stop the system tracing if a
87 [root@f32 ~]# cd /sys/kernel/tracing/
88 [root@f32 tracing]# echo timerlat > current_tracer
89 [root@f32 tracing]# echo 1 > events/osnoise/enable
[all …]
|
| H A D | uprobetracer.rst | 2 Uprobe-tracer: Uprobe-based Event Tracing
15 /sys/kernel/tracing/uprobe_events, and enable it via
16 /sys/kernel/tracing/events/uprobes/<EVENT>/enable.
21 You can also use /sys/kernel/tracing/dynamic_events instead of
82 /sys/kernel/tracing/uprobe_profile. The first column is the filename,
90 echo 'p /bin/bash:0x4245c0' > /sys/kernel/tracing/uprobe_events
94 echo 'r /bin/bash:0x4245c0' > /sys/kernel/tracing/uprobe_events
98 echo '-:p_bash_0x4245c0' >> /sys/kernel/tracing/uprobe_events
102 cat /sys/kernel/tracing/uprobe_events
106 echo > /sys/kernel/tracing/uprobe_events
[all …]
|
| H A D | hwlat_detector.rst | 38 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 D | debugging.rst | 15 The tracing infrastructure can be very useful for debugging the Linux
21 $ sudo mount -t tracefs tracefs /sys/kernel/tracing
30 written to the tracing ring buffer in a lockless way. To make it even
62 The tracing ring buffer, by default, is a circular buffer than will
67 this. The first is "ftrace_dump_on_oops". This will dump the tracing ring
76 Note, the tracing buffer is made up of per CPU buffers where each of these
83 If the system memory allows it, the tracing ring buffer can be specified at
85 the memory is not modified, the tracing buffer can be retrieved from the
141 By default, the content of trace_printk() goes into the top level tracing
143 trace_printk() content, and some other internal tracing go to the preserved
[all …]
|
| H A D | kprobetrace.rst | 2 Kprobe-based Event Tracing
20 /sys/kernel/tracing/kprobe_events, and enable it via
21 /sys/kernel/tracing/events/kprobes/<EVENT>/enable.
23 You can also use /sys/kernel/tracing/dynamic_events instead of
155 under tracing/events/kprobes/<EVENT>, at the directory you can see 'id',
177 /sys/kernel/tracing/kprobe_profile.
201 …echo 'p:myprobe do_sys_open dfd=%ax filename=%dx flags=%cx mode=+4($stack)' > /sys/kernel/tracing/…
211 echo 'r:myretprobe do_sys_open $retval' >> /sys/kernel/tracing/kprobe_events
216 /sys/kernel/tracing/events/kprobes/<EVENT>/format.
219 cat /sys/kernel/tracing/events/kprobes/myprobe/format
[all …]
|
| H A D | histogram.rst | 98 tracing code. Trying to apply that comm value to other pid
106 /sys/kernel/tracing/events/net/netif_rx/trigger
108 # cat /sys/kernel/tracing/events/net/netif_rx/hist
111 /sys/kernel/tracing/events/net/netif_rx/trigger
162 Instead of enabling or disabling the tracing of the target event
173 /sys/kernel/tracing/events/net/netif_receive_skb/trigger
176 /sys/kernel/tracing/events/sched/sched_process_exec/trigger
179 /sys/kernel/tracing/events/sched/sched_process_exit/trigger
212 tracing/error_log file. See Error Conditions in
222 # cat /sys/kernel/tracing/events/kmem/kmalloc/format
[all …]
|
| /linux/Documentation/core-api/irq/ |
| H A D | irqflags-tracing.rst | 2 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
|
| /linux/tools/testing/selftests/powerpc/mm/ |
| H A D | stress_code_patching.sh | 13 if [ ! -e "$DEBUFS_DIR/tracing/current_tracer" ]
15 echo "Tracing files not found, skipping" 1>&2
22 if grep -q "FUNCTION TRACING IS CORRUPTED" "$DEBUFS_DIR/tracing/trace"
33 echo function > $DEBUFS_DIR/tracing/current_tracer
34 echo nop > $DEBUFS_DIR/tracing/current_tracer
41 echo nop > $DEBUFS_DIR/tracing/current_tracer
|
| /linux/Documentation/firmware-guide/acpi/ |
| H A D | method-tracing.rst | 15 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 …]
|
| /linux/tools/testing/selftests/ftrace/test.d/00basic/ |
| H A D | snapshot.tc | 2 # description: Snapshot and tracing setting
6 echo "Set tracing off"
15 echo "Ensure keep tracing off"
18 echo "Set tracing on"
24 echo "Ensure keep tracing on"
|
| /linux/drivers/staging/media/atomisp/pci/runtime/debug/interface/ |
| H A D | ia_css_debug.h | 35 /*! Level for tracing errors */
37 /*! Level for tracing warnings */
39 /*! Level for tracing debug messages */
41 /*! Level for tracing trace messages a.o. ia_css public function calls */
43 /*! Level for tracing trace messages a.o. ia_css private function calls */
45 /*! Level for tracing parameter messages e.g. in and out params of functions */
47 /*! Level for tracing info messages */
50 /* Global variable which controls the verbosity levels of the debug tracing */
127 /*! @brief Function for tracing to the provided printf function in the
166 * Dumps the sp software state to tracing output.
[all …]
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| H A D | trace_ext.c | 69 /* open tracing */ in test_trace_ext()
71 if (CHECK(!skel_trace, "setup", "tracing/test_pkt_md_access_new open failed\n")) in test_trace_ext()
74 /* set tracing's attach target - fentry */ in test_trace_ext()
78 /* set tracing's attach target - fexit */ in test_trace_ext()
82 /* load/attach tracing */ in test_trace_ext()
84 if (!ASSERT_OK(err, "tracing/test_pkt_md_access_new load")) { in test_trace_ext()
91 if (!ASSERT_OK(err, "tracing/test_pkt_md_access_new attach")) in test_trace_ext()
|
| /linux/tools/testing/selftests/user_events/ |
| H A D | user_events_selftests.h | 16 umount("/sys/kernel/tracing"); in tracefs_unmount()
29 ret = stat("/sys/kernel/tracing", &buf); in tracefs_enabled()
37 ret = stat("/sys/kernel/tracing/README", &buf); in tracefs_enabled()
40 if (mount(NULL, "/sys/kernel/tracing", "tracefs", 0, NULL) != 0) { in tracefs_enabled()
48 ret = stat("/sys/kernel/tracing/README", &buf); in tracefs_enabled()
79 ret = stat("/sys/kernel/tracing/user_events_data", &buf); in user_events_enabled()
|
| /linux/include/asm-generic/ |
| H A D | syscall.h | 28 * tracing about to attempt one, returns the system call number.
42 * @task: task of interest, must be in system call exit tracing
46 * call exit tracing (due to %SYSCALL_WORK_SYSCALL_TRACE or
54 * register state looked like at system call entry tracing.
65 * It's only valid to call this when @task is stopped for tracing on exit
79 * It's only valid to call this when @task is stopped for tracing on exit
97 * It's only valid to call this when @task is stopped for tracing on exit
113 * It's only valid to call this when @task is stopped for tracing on
|
| /linux/drivers/char/mwave/ |
| H A D | README | 8 0x0001 mwavedd api tracing
9 0x0002 smapi api tracing
10 0x0004 3780i tracing
11 0x0008 tp3780i tracing
13 Tracing only occurs if the driver has been compiled with the
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | verifier_helper_restricted.c | 89 __failure __msg("tracing progs cannot use bpf_timer yet")
114 __failure __msg("tracing progs cannot use bpf_timer yet")
139 __failure __msg("tracing progs cannot use bpf_timer yet")
164 __failure __msg("tracing progs cannot use bpf_timer yet")
189 __failure __msg("tracing progs cannot use bpf_spin_lock yet")
212 __failure __msg("tracing progs cannot use bpf_spin_lock yet")
235 __failure __msg("tracing progs cannot use bpf_spin_lock yet")
258 __failure __msg("tracing progs cannot use bpf_spin_lock yet")
|
| /linux/Documentation/translations/zh_CN/core-api/irq/ |
| H A D | irqflags-tracing.rst | 3 :Original: Documentation/core-api/irq/irqflags-tracing.rst
9 .. _cn_irqflags-tracing.rst:
17 “irq-flags tracing”（中断标志追踪）功能可以 “追踪” hardirq和softirq的状态，它让
27 的状态变化。但是一个架构可以以一种相当直接且无风险的方式启用irq-flags-tracing。
|
| /linux/drivers/net/wireless/broadcom/brcm80211/ |
| H A D | Kconfig | 28 bool "Broadcom device tracing"
30 depends on TRACING
34 Tracing can be enabled at runtime to aid in debugging wireless
35 issues. This option adds a small amount of overhead when tracing
|