| /OK3568_Linux_fs/kernel/kernel/trace/ |
| H A D | Kconfig | 87 Adds a very slight overhead to tracing when enabled.
90 bool "Register read/write tracing"
91 depends on TRACING
100 select TRACING
109 Provides an option to not automount tracefs in /sys/kernel/debug/tracing.
112 # enabled by all tracers (context switch and event tracer) they select TRACING.
115 # GENERIC_TRACER and TRACING to avoid circular dependencies to accomplish the
118 config TRACING config
130 select TRACING
134 # be able to offer generic tracing facilities:
[all …]
|
| H A D | trace_selftest.c | 53 /* disable tracing */ in trace_test_buffer_cpu()
338 /* enable tracing, and record the filter function */ in trace_selftest_startup_dynamic_tracing()
354 /* enable tracing */ in trace_selftest_startup_dynamic_tracing()
381 /* stop the tracing. */ in trace_selftest_startup_dynamic_tracing()
399 /* Test the ops with global tracing running */ in trace_selftest_startup_dynamic_tracing()
406 /* Enable tracing on all functions again */ in trace_selftest_startup_dynamic_tracing()
409 /* Test the ops with global tracing off */ in trace_selftest_startup_dynamic_tracing()
442 * tracing utility. in trace_selftest_test_recursion_safe_func()
471 /* enable tracing, and record the filter function */ in trace_selftest_function_recursion()
585 /* enable tracing, and record the filter function */ in trace_selftest_function_regs()
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/trace/ |
| 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 | 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 …]
|
| 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/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 …]
|
| H A 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 …]
|
| H A 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 …]
|
| 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 | 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 …]
|
| 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 …]
|
| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/kernel/drivers/staging/media/atomisp/pci/runtime/debug/interface/ |
| H A D | ia_css_debug.h | 34 /*! Level for tracing errors */
36 /*! Level for tracing warnings */
38 /*! Level for tracing debug messages */
40 /*! Level for tracing trace messages a.o. ia_css public function calls */
42 /*! Level for tracing trace messages a.o. ia_css private function calls */
44 /*! Level for tracing parameter messages e.g. in and out params of functions */
46 /*! Level for tracing info messages */
49 /* Global variable which controls the verbosity levels of the debug tracing */
126 /*! @brief Function for tracing to the provided printf function in the
163 * Dumps the isp hardware state to tracing output.
[all …]
|
| /OK3568_Linux_fs/u-boot/doc/ |
| H A D | README.trace | 7 Tracing in U-Boot
10 U-Boot supports a simple tracing feature which allows a record of excecution
33 way of trying out tracing before you use it on your actual board. To do
45 Build sandbox U-Boot with tracing enabled:
122 used after relocation, as a place to put function tracing
127 Define this to start tracing early, before relocation.
141 Building U-Boot with Tracing Enabled
161 effect. Once you have done your optimisations, turn off tracing before
164 The best time to start tracing is right at the beginning of U-Boot. The
165 best time to stop tracing is right at the end. In practice it is hard
[all …]
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/kernel/arch/nds32/include/asm/ |
| H A D | syscall.h | 19 * tracing about to attempt one, returns the system call number.
37 * @task: task of interest, must be in system call exit tracing
41 * call exit tracing (due to TIF_SYSCALL_TRACE or TIF_SYSCALL_AUDIT),
49 * register state looked like at system call entry tracing.
64 * It's only valid to call this when @task is stopped for tracing on exit
82 * It's only valid to call this when @task is stopped for tracing on exit
103 * It's only valid to call this when @task is stopped for tracing on exit
122 * It's only valid to call this when @task is stopped for tracing on
137 * @task: task of interest, must be in system call entry tracing
144 * It's only valid to call this when @task is stopped for tracing on
|
| /OK3568_Linux_fs/kernel/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 TIF_SYSCALL_TRACE or TIF_SYSCALL_AUDIT),
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
78 * It's only valid to call this when @task is stopped for tracing on exit
95 * It's only valid to call this when @task is stopped for tracing on exit
110 * It's only valid to call this when @task is stopped for tracing on
118 * @task: task of interest, must be in system call entry tracing
125 * It's only valid to call this when @task is stopped for tracing on
|
| /OK3568_Linux_fs/kernel/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"
|
| /OK3568_Linux_fs/kernel/include/linux/ |
| H A D | tracehook.h | 3 * Tracing hooks
8 * user tracing/debugging support might need to do something. These
15 * fast path when no tracing is enabled should be very short.
19 * user debugging or tracing facility (such as ptrace). The interfaces
22 * tracing facilities. Likewise, maintainers of the tracing code do not
28 * core code changing should notify the maintainers of the tracing code
31 * Some tracehook_*() inlines take arguments that the current tracing
35 * core code won't have to be updated when tracing adds more features.
40 * tracing code that they need to work out the change.
|
| /OK3568_Linux_fs/kernel/tools/testing/selftests/bpf/prog_tests/ |
| H A D | trace_ext.c | 65 /* open tracing */ in test_trace_ext()
67 if (CHECK(!skel_trace, "setup", "tracing/test_pkt_md_access_new open failed\n")) in test_trace_ext()
70 /* set tracing's attach target - fentry */ in test_trace_ext()
74 /* set tracing's attach target - fexit */ in test_trace_ext()
78 /* load/attach tracing */ in test_trace_ext()
80 if (CHECK(err, "setup", "tracing/test_pkt_md_access_new load failed\n")) { in test_trace_ext()
87 if (CHECK(err, "setup", "tracing/test_pkt_md_access_new attach failed: %d\n", err)) in test_trace_ext()
|
| /OK3568_Linux_fs/kernel/tools/lib/traceevent/Documentation/ |
| H 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));
|
| /OK3568_Linux_fs/kernel/tools/lib/api/fs/ |
| H A D | tracing_path.c | 17 static char tracing_path[PATH_MAX] = "/sys/kernel/debug/tracing";
18 static char tracing_events_path[PATH_MAX] = "/sys/kernel/debug/tracing/events";
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()
50 __tracing_path_set("tracing/", mnt); in tracing_path_debugfs_mount()
70 __tracing_path_set("tracing/", mntpt); in tracing_path_set()
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/doc/gdb/ |
| H A D | disconnected-tracing.html | 18 <title>Debugging with GDB: disconnected tracing</title>
20 <meta name="description" content="Debugging with GDB: disconnected tracing">
21 <meta name="keywords" content="Debugging with GDB: disconnected tracing">
55 …equiv="Refresh" content="0; url=Starting-and-Stopping-Trace-Experiments.html#disconnected-tracing">
61 …ef="Starting-and-Stopping-Trace-Experiments.html#disconnected-tracing">disconnected tracing</a>.</…
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/share/doc/gdb/ |
| H A D | disconnected-tracing.html | 18 <title>Debugging with GDB: disconnected tracing</title>
20 <meta name="description" content="Debugging with GDB: disconnected tracing">
21 <meta name="keywords" content="Debugging with GDB: disconnected tracing">
55 …equiv="Refresh" content="0; url=Starting-and-Stopping-Trace-Experiments.html#disconnected-tracing">
61 …ef="Starting-and-Stopping-Trace-Experiments.html#disconnected-tracing">disconnected tracing</a>.</…
|