Searched full:tracing (Results 1 – 25 of 86) sorted by relevance
1234
| /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 | 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 | 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/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
[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/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
[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/debug/tracing/available_events.
30 to /sys/kernel/debug/tracing/set_event. For example::
32 # echo sched_wakeup >> /sys/kernel/debug/tracing/set_event
[all …]
|
| D | kprobetrace.rst | 2 Kprobe-based Event Tracing
20 /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
[all …]
|
| D | events-msr.rst | 5 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
|
| D | events-nmi.rst | 7 /sys/kernel/debug/tracing/events/nmi
34 cd /sys/kernel/debug/tracing/events/nmi/nmi_handler
40 $ cat /sys/kernel/debug/tracing/trace_pipe
|
| D | histogram.rst | 94 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 …]
|
| 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
174 If this is set on any ftrace ops, then the tracing cannot disabled by
204 Filters denote which functions should be enabled when tracing is enabled.
205 If @buf is NULL and reset is set, all functions will be enabled for tracing.
|
| D | index.rst | 2 Linux Tracing Technologies
|
| D | tracepoint-analysis.rst | 11 tracing infrastructure.
20 the appropriate tracing options have been configured into the kernel. It is
29 All possible events are visible from /sys/kernel/debug/tracing/events. Simply
32 $ find /sys/kernel/debug/tracing/events -type d
62 $ for i in `find /sys/kernel/debug/tracing/events -name "enable" | grep mm_`; do echo 1 > $i; done
192 /sys/kernel/debug/tracing/trace_pipe in human-readable format although binary
|
| D | ftrace-design.rst | 14 Here we will cover the architecture pieces that the common function tracing
22 Ideally, everyone who wishes to retain performance while supporting tracing in
73 your system when tracing is disabled. So the start of the mcount function is
235 You need very few things to get the syscalls tracing in an arch.
242 in the ptrace syscalls tracing path.
365 is what helps us retain runtime performance when not tracing). The second is
|
| /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 …]
|
| D | index.rst | 17 method-tracing
|
| /Documentation/networking/device_drivers/ethernet/mellanox/ |
| D | mlx5.rst | 284 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 …]
|
| /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 …]
|
| D | sysfs-bus-intel_th-devices-msc | 20 provided there are no active users and tracing is not enabled,
35 there are no active users and tracing is not enabled) and then
|
| D | sysfs-class-stm_source | 6 stm_source device linkage to stm device, where its tracing data
|
| /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,
359 comparator with "_stext" and "_etext", essentially tracing any instruction
398 Info Tracing enabled
443 Info Tracing enabled
[all …]
|
| /Documentation/input/devices/ |
| D | appletouch.rst | 80 deactivates any debugging, 1 activates tracing of invalid samples, 2 activates
81 full tracing (each sample is being traced)::
|
| /Documentation/scsi/ |
| D | advansys.rst | 82 Enabling this option adds tracing functions to the driver and the
83 ability to set a driver tracing level at boot time. This option is
113 1 High-Level Tracing
114 2-N Verbose Tracing
|
1234