Searched full:tracing (Results 1 – 25 of 138) sorted by relevance
123456
| /Documentation/networking/device_drivers/ethernet/mellanox/mlx5/ |
| 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 …]
|
| /Documentation/core-api/irq/ |
| 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
|
| D | index.rst | 11 irqflags-tracing
|
| /Documentation/trace/ |
| 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 …]
|
| 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 …]
|
| 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:
|
| 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 …]
|
| 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 …]
|
| 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 …]
|
| 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 …]
|
| 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
|
| 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 …]
|
| 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
|
| 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
134 Additional Tracing
173 approach: measuring thread and tracing.
|
| D | user_events.rst | 2 user_events: User-based Event Tracing
14 /sys/kernel/tracing/user_events_status and can both register and write
15 data out via /sys/kernel/tracing/user_events_data.
17 Programs can also use /sys/kernel/tracing/dynamic_events to register and
27 on the /sys/kernel/tracing/user_events_data file.
38 /sys/kernel/tracing/user_events_data file. The command to issue is
121 events need to use /sys/kernel/tracing/events/user_events/[name]/enable
168 /sys/kernel/tracing/user_events_data file. The command to issue is
183 be deleted then the /sys/kernel/tracing/dynamic_events file should be used for
189 be disabled via ioctl() out to the /sys/kernel/tracing/user_events_data file.
|
| 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 …]
|
| 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 …]
|
| D | ftrace-uses.rst | 58 To enable tracing call::
62 To disable tracing call::
108 at the start of the function where ftrace was tracing. Otherwise it
134 function that the callback is tracing. Note, on success,
220 If this is set on any ftrace ops, then the tracing cannot disabled by
250 Filters denote which functions should be enabled when tracing is enabled.
251 If @buf is NULL and reset is set, all functions will be enabled for tracing.
|
| /Documentation/firmware-guide/acpi/ |
| 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 …]
|
| /Documentation/translations/zh_CN/core-api/irq/ |
| 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。
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-coresight-devices-etm4x | 5 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 …]
|
| /Documentation/core-api/ |
| D | entry.rst | 11 * Tracing
86 * Tracing
89 syscall tracing, etc. After all that is done, the instrumentable invoke_syscall
94 returning to user space like tracing, audit, signals, task work etc. After
98 * Tracing
140 already be watching. Lockdep and tracing have to be updated unconditionally.
218 * Tracing
|
| /Documentation/trace/coresight/ |
| D | coresight.rst | 2 Coresight - HW Assisted Tracing on ARM
12 based SoC. It includes solutions for JTAG and HW assisted tracing. This
15 HW assisted tracing is becoming increasingly useful when dealing with systems
17 developed a HW assisted tracing solution by means of different components, each
18 being added to a design at synthesis time to cater to specific tracing needs.
23 path based on tracing scenarios as configured by users. From there the stream
89 the basic tracing functionality, enabling components such ETM/PTM, funnel,
361 comparator with "_stext" and "_etext", essentially tracing any instruction
400 Info Tracing enabled
445 Info Tracing enabled
[all …]
|
| /Documentation/tools/rtla/ |
| D | rtla-timerlat-top.rst | 37 Set stop tracing conditions and run without collecting and displaying statistics.
38 Print the auto-analysis if the system hits the stop tracing condition. This option
76 rtla timerlat hit stop tracing
77 ## CPU 23 hit stop tracing, analyzing it ##
|
| /Documentation/admin-guide/media/ |
| D | visl.rst | 18 debugfs interface. This is in many ways similar to the tracing
40 frames where dprintk is activated. This only controls the dprintk tracing on a
90 $ ls /sys/kernel/tracing/events/ | grep visl
103 $ echo 1 > /sys/kernel/tracing/events/visl_hevc_controls/v4l2_ctrl_hevc_sps/enable
109 $ cat /sys/kernel/tracing/trace
|
123456