| /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/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。
33 然后还需要做一些功能上的改变来实现对irq-flags-tracing的支持:
45 一般来说，在一个架构中，不完整的irq-flags-tracing实现是没有风险的：lockdep
46 会检测到这一点，并将自己关闭。即锁验证器仍然可靠。应该不会因为irq-tracing的错
|
| /linux/Documentation/ABI/obsolete/ |
| H A D | automount-tracefs-debugfs | 1 What: /sys/kernel/debug/tracing
8 into the debugfs file system under the "tracing" directory. Access
9 to the files were in /sys/kernel/debug/tracing. As systems wanted
10 access to the tracing interface without having to enable debugfs, a
12 file system and was usually mounted in /sys/kernel/tracing.
16 the "tracing" directory of debugfs. The tracefs interface was added
19 All tooling should now be using tracefs directly and the "tracing"
|
| /linux/Documentation/trace/ |
| H A D | index.rst | 7 behavior. This guide provides documentation on various tracing
13 This section provides an overview of Linux tracing mechanisms
27 The following are the primary tracing frameworks integrated into
46 A detailed explanation of event tracing mechanisms and their
64 This section covers tracing features that monitor hardware
84 These tools allow tracing user-space applications and
97 tracing tool and framework.
|
| 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 | 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
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
63 $ cat /sys/kernel/tracing/trace_pipe > mydump.txt &
[all …]
|
| H A D | uprobetracer.rst | 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
111 # cd /sys/kernel/tracing/
[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 | kprobetrace.rst | 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
242 echo > /sys/kernel/tracing/kprobe_events
[all …]
|
| H A D | events-msr.rst | 5 The x86 kernel supports tracing most MSR (Model Specific Register) accesses.
11 /sys/kernel/tracing/events/msr/
37 cat /sys/kernel/tracing/trace | decode_msr.py /usr/src/linux/include/asm/msr-index.h
|
| H A D | events-nmi.rst | 7 /sys/kernel/tracing/events/nmi
34 cd /sys/kernel/tracing/events/nmi/nmi_handler
40 $ cat /sys/kernel/tracing/trace_pipe
|
| H A D | ftrace.rst | 27 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 D | osnoise-tracer.rst | 47 tracing system (generally mounted at /sys/kernel/tracing).
51 [root@f32 ~]# cd /sys/kernel/tracing/
52 [root@f32 tracing]# echo osnoise > current_tracer
56 [root@f32 tracing]# cat trace
103 - osnoise/stop_tracing_us: stop the system tracing if a single noise
106 - osnoise/stop_tracing_total_us: stop the system tracing if total noise
173 approach: measuring thread and tracing.
|
| /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/perf/tests/shell/common/ |
| H A D | init.sh | 125 test -e /sys/kernel/debug/tracing/kprobe_events
130 test -e /sys/kernel/debug/tracing/uprobe_events
135 echo 0 > /sys/kernel/debug/tracing/events/enable
136 check_kprobes_available && echo > /sys/kernel/debug/tracing/kprobe_events
137 check_uprobes_available && echo > /sys/kernel/debug/tracing/uprobe_events
|
| /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/powerpc/mm/ |
| H A D | stress_code_patching.sh | 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/tools/testing/selftests/bpf/ |
| H A D | test_ftrace.sh | 3 if [[ -e /sys/kernel/tracing/trace ]]; then
4 TR=/sys/kernel/tracing/
6 TR=/sys/kernel/debug/tracing/
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-class-intel_pmt-features | 24 ├── tracing/ # PMT tracing features
96 ├── tracing/
114 Example 'caps' content for the 'tracing' feature:
117 ├── tracing/
127 tracing Available: No
|
| /linux/kernel/trace/ |
| H A D | Kconfig | 157 Adds a very slight overhead to tracing when enabled.
192 # be able to offer generic tracing facilities:
205 Enable the kernel tracing infrastructure.
214 The tracing interface was moved from /sys/kernel/debug/tracing
215 to /sys/kernel/tracing in 2015, but the tracing file system
228 kernel cmdline at boot time for debugging (tracing) driver
245 tracing is enabled by the administrator. If it's runtime disabled
303 This option will modify all the calls to function tracing
312 See the files in /sys/kernel/tracing:
318 otherwise has native performance as long as no tracing is active.
[all …]
|
| /linux/tools/testing/ktest/examples/include/ |
| H A D | bootconfig.conf | 60 TEST_NAME = bootconfig tracing
62 BOOTCONFIG_FILE = tracing.bconf
63 BOOTCONFIG_VERIFY = verify-tracing.sh
|
| /linux/Documentation/filesystems/nfs/ |
| H A D | nfsd-io-modes.rst | 140 echo 1 > /sys/kernel/tracing/events/nfsd/nfsd_read_vector/enable
141 echo 1 > /sys/kernel/tracing/events/nfsd/nfsd_read_direct/enable
142 echo 1 > /sys/kernel/tracing/events/nfsd/nfsd_read_io_done/enable
143 echo 1 > /sys/kernel/tracing/events/xfs/xfs_file_direct_read/enable
150 echo 1 > /sys/kernel/tracing/events/nfsd/nfsd_write_opened/enable
151 echo 1 > /sys/kernel/tracing/events/nfsd/nfsd_write_direct/enable
152 echo 1 > /sys/kernel/tracing/events/nfsd/nfsd_write_io_done/enable
153 echo 1 > /sys/kernel/tracing/events/xfs/xfs_file_direct_write/enable
|
| /linux/Documentation/tools/rtla/ |
| H A D | rtla-timerlat-top.rst | 39 Set stop tracing conditions and run without collecting and displaying statistics.
40 Print the auto-analysis if the system hits the stop tracing condition. This option
78 rtla timerlat hit stop tracing
79 ## CPU 23 hit stop tracing, analyzing it ##
|
| H A D | common_appendix.txt | 8 0 Passed: the test did not hit the stop tracing condition
10 2 Failed: the test hit the stop tracing condition
|
| /linux/arch/powerpc/platforms/powernv/ |
| H A D | Kconfig | 32 bool "Enable runtime allocation of RAM for tracing"
36 for hardware tracing.
|