| /linux-5.15/Documentation/translations/zh_CN/core-api/irq/ |
| 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-5.15/k_shared/ |
| A D | ftrace.sh | 7 cd /sys/kernel/debug/tracing
12 echo 1 > /sys/kernel/debug/tracing/events/oom/oom_score_adj_update/enable
13 echo 1 > /sys/kernel/debug/tracing/events/vmscan/mm_shrink_slab_start/enable
14 echo 1 > /sys/kernel/debug/tracing/events/vmscan/mm_shrink_slab_end/enable
24 cat /sys/kernel/debug/tracing/trace > /data/ftrace_.$TIMES
|
| /linux-5.15/Documentation/trace/ |
| 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 - osnoise/stop_tracing_us: stop the system tracing if a
74 - stop_tracing_total_us: stop the system tracing if a
86 [root@f32 ~]# cd /sys/kernel/tracing/
87 [root@f32 tracing]# echo timerlat > current_tracer
88 [root@f32 tracing]# echo 1 > events/osnoise/enable
[all …]
|
| 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 …]
|
| 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/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 …]
|
| A D | uprobetracer.rst | 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
111 # cd /sys/kernel/debug/tracing/
[all …]
|
| 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:
|
| A D | events.rst | 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.
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 …]
|
| A 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
|
| A D | kprobetrace.rst | 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
214 echo > /sys/kernel/debug/tracing/kprobe_events
[all …]
|
| A D | histogram.rst | 95 tracing code. Trying to apply that comm value to other pid
103 /sys/kernel/debug/tracing/events/net/netif_rx/trigger
105 # cat /sys/kernel/debug/tracing/events/net/netif_rx/hist
108 /sys/kernel/debug/tracing/events/net/netif_rx/trigger
153 Instead of enabling or disabling the tracing of the target event
164 /sys/kernel/debug/tracing/events/net/netif_receive_skb/trigger
167 /sys/kernel/debug/tracing/events/sched/sched_process_exec/trigger
170 /sys/kernel/debug/tracing/events/sched/sched_process_exit/trigger
203 tracing/error_log file. See Error Conditions in
213 # cat /sys/kernel/debug/tracing/events/kmem/kmalloc/format
[all …]
|
| A 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
|
| 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 …]
|
| 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
152 approach: measuring thread and tracing.
|
| /linux-5.15/Documentation/core-api/irq/ |
| 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-5.15/tools/lib/traceevent/Documentation/ |
| A D | libtraceevent-cpus.txt | 6 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));
|
| /linux-5.15/Documentation/firmware-guide/acpi/ |
| 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-5.15/tools/testing/selftests/powerpc/mm/ |
| 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-5.15/arch/s390/kernel/ |
| H A D | head64.S | 54 .quad 0 # cr9: tracing off
55 .quad 0 # cr10: tracing off
56 .quad 0 # cr11: tracing off
57 .quad 0 # cr12: tracing off
|
| /linux-5.15/Documentation/networking/device_drivers/ethernet/mellanox/ |
| A D | mlx5.rst | 565 For the list of support mlx5 events check /sys/kernel/debug/tracing/events/mlx5/
571 $ echo mlx5:mlx5e_configure_flower >> /sys/kernel/debug/tracing/set_event
572 $ cat /sys/kernel/debug/tracing/trace
578 $ echo mlx5:mlx5e_delete_flower >> /sys/kernel/debug/tracing/set_event
579 $ cat /sys/kernel/debug/tracing/trace
585 $ echo mlx5:mlx5e_stats_flower >> /sys/kernel/debug/tracing/set_event
586 $ cat /sys/kernel/debug/tracing/trace
592 $ echo mlx5:mlx5e_tc_update_neigh_used_value >> /sys/kernel/debug/tracing/set_event
593 $ cat /sys/kernel/debug/tracing/trace
599 $ echo mlx5:mlx5e_rep_neigh_update >> /sys/kernel/debug/tracing/set_event
[all …]
|
| /linux-5.15/tools/testing/ktest/examples/include/ |
| A D | bootconfig.conf | 60 TEST_NAME = bootconfig tracing
62 BOOTCONFIG_FILE = tracing.bconf
63 BOOTCONFIG_VERIFY = verify-tracing.sh
|
| /linux-5.15/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
|
| /linux-5.15/tools/lib/api/fs/ |
| A D | tracing_path.c | 20 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()
|
| /linux-5.15/kernel/trace/ |
| H A D | Kconfig | 96 Adds a very slight overhead to tracing when enabled.
130 # be able to offer generic tracing facilities:
143 Enable the kernel tracing infrastructure.
153 kernel cmdline at boot time for debugging (tracing) driver
170 tracing is enabled by the administrator. If it's runtime disabled
189 bool "enable/disable function tracing dynamically"
194 This option will modify all the calls to function tracing
203 See the files in /sys/kernel/debug/tracing:
209 otherwise has native performance as long as no tracing is active.
248 kernel and displays it in /sys/kernel/debug/tracing/stack_trace.
[all …]
|
| /linux-5.15/Documentation/ABI/testing/ |
| A 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 …]
|