Searched refs:tracing (Results 1 – 25 of 135) sorted by relevance
123456
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 the18 tracing information should be printed.26 The events which are available for tracing can be found in the file27 /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_event39 # echo '!sched_wakeup' >> /sys/kernel/debug/tracing/set_event43 # echo > /sys/kernel/debug/tracing/set_event[all …]
2 In-kernel memory-mapped I/O tracing10 MMIO tracing was originally developed by Intel around 2003 for their Fault12 Jeff Muizelaar created a tool for tracing MMIO accesses with the Nouveau28 supported, but tracing is unreliable and may miss events if more than one CPU39 $ echo mmiotrace > /sys/kernel/debug/tracing/current_tracer40 $ cat /sys/kernel/debug/tracing/trace_pipe > mydump.txt &42 $ echo "X is up" > /sys/kernel/debug/tracing/trace_marker43 $ echo nop > /sys/kernel/debug/tracing/current_tracer59 $ echo mmiotrace > /sys/kernel/debug/tracing/current_tracer63 $ cat /sys/kernel/debug/tracing/trace_pipe > mydump.txt &[all …]
20 /sys/kernel/debug/tracing/kprobe_events, and enable it via21 /sys/kernel/debug/tracing/events/kprobes/<EVENT>/enable.83 under tracing/events/kprobes/<EVENT>, at the directory you can see 'id',105 /sys/kernel/debug/tracing/kprobe_profile.115 …_sys_open dfd=%ax filename=%dx flags=%cx mode=+4($stack)' > /sys/kernel/debug/tracing/kprobe_events125 echo 'r:myretprobe do_sys_open $retval' >> /sys/kernel/debug/tracing/kprobe_events130 /sys/kernel/debug/tracing/events/kprobes/<EVENT>/format.133 cat /sys/kernel/debug/tracing/events/kprobes/myprobe/format156 echo > /sys/kernel/debug/tracing/kprobe_events167 Right after definition, each event is disabled by default. For tracing these[all …]
38 Write the ASCII text "hwlat" into the current_tracer file of the tracing system39 (mounted at /sys/kernel/tracing or /sys/kernel/tracing). It is possible to45 # echo hwlat > /sys/kernel/tracing/current_tracer46 # echo 100 > /sys/kernel/tracing/tracing_thresh48 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:
15 /sys/kernel/debug/tracing/uprobe_events, and enable it via16 /sys/kernel/debug/tracing/events/uprobes/<EVENT>/enable.73 /sys/kernel/debug/tracing/uprobe_profile.82 echo 'p /bin/bash:0x4245c0' > /sys/kernel/debug/tracing/uprobe_events86 echo 'r /bin/bash:0x4245c0' > /sys/kernel/debug/tracing/uprobe_events90 echo '-:p_bash_0x4245c0' >> /sys/kernel/debug/tracing/uprobe_events94 cat /sys/kernel/debug/tracing/uprobe_events98 echo > /sys/kernel/debug/tracing/uprobe_events103 # cd /sys/kernel/debug/tracing/147 Right after definition, each event is disabled by default. For tracing these[all …]
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
94 tracing code. Trying to apply that comm value to other pid102 /sys/kernel/debug/tracing/events/net/netif_rx/trigger104 # cat /sys/kernel/debug/tracing/events/net/netif_rx/hist107 /sys/kernel/debug/tracing/events/net/netif_rx/trigger152 Instead of enabling or disabling the tracing of the target event163 /sys/kernel/debug/tracing/events/net/netif_receive_skb/trigger166 /sys/kernel/debug/tracing/events/sched/sched_process_exec/trigger169 /sys/kernel/debug/tracing/events/sched/sched_process_exit/trigger210 # echo xxx > /sys/kernel/debug/tracing/events/sched/sched_wakeup/trigger213 # cat /sys/kernel/debug/tracing/events/sched/sched_wakeup/hist[all …]
7 /sys/kernel/debug/tracing/events/nmi34 cd /sys/kernel/debug/tracing/events/nmi/nmi_handler40 $ cat /sys/kernel/debug/tracing/trace_pipe
27 is really a frame work of several assorted tracing utilities.28 There's latency tracing to examine what occurs between interrupts32 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 mount56 tracefs /sys/kernel/tracing tracefs defaults 0 060 mount -t tracefs nodev /sys/kernel/tracing65 ln -s /sys/kernel/tracing /tracing69 Before 4.1, all ftrace tracing control files were within the debugfs70 file system, which is typically located at /sys/kernel/debug/tracing.74 /sys/kernel/debug/tracing[all …]
2 IRQ-flags state tracing7 The "irq-flags tracing" feature "traces" hardirq and softirq state, in21 state changes. But an architecture can be irq-flags-tracing enabled in a30 irq-flags-tracing support:37 irq-flags-tracing is spent in this state: look at the lockdep40 lockdep complaint in the irq-flags-tracing functions arch support is43 excluded from the irq-tracing [and lock validation] mechanism via46 In general there is no risk from having an incomplete irq-flags-tracing49 should be no crashes due to irq-tracing bugs. (except if the assembly
10 tracing facility.14 ACPICA provides method tracing capability. And two functions are63 There are special log entries added by the method tracing facility at125 Note that all above method tracing facility related module parameters can132 All method tracing functions can be configured via ACPI module141 The temporary debug_layer used when the tracing feature is enabled.146 The temporary debug_level used when the tracing feature is enabled.151 The status of the tracing feature.152 Users can enable/disable this debug tracing feature by executing157 Disable the method tracing feature.[all …]
8 0x0001 mwavedd api tracing9 0x0002 smapi api tracing10 0x0004 3780i tracing11 0x0008 tp3780i tracing
70 which allows tracing the instructions that a processor is executing71 This is primarily useful for instruction level tracing. Depending72 the ETM version data tracing may also be available.79 This driver provides support for the ETM4.x tracer module, tracing the81 for instruction level tracing. Depending on the implemented version82 data tracing may also be available.99 instrumentation based tracing. This is primarily used for
20 static void __tracing_path_set(const char *tracing, const char *mountpoint) in __tracing_path_set() argument24 mountpoint, tracing); in __tracing_path_set()26 mountpoint, tracing, "events"); in __tracing_path_set()
77 .quad 0 # cr9: tracing off78 .quad 0 # cr10: tracing off79 .quad 0 # cr11: tracing off80 .quad 0 # cr12: tracing off
88 Adds a very slight overhead to tracing when enabled.123 # be able to offer generic tracing facilities:137 Enable the kernel tracing infrastructure.154 tracing is enabled by the administrator. If it's runtime disabled185 Enable tracing of disable and enable events for preemption and irqs.206 echo 0 > /sys/kernel/debug/tracing/tracing_max_latency231 echo 0 > /sys/kernel/debug/tracing/tracing_max_latency259 Some files are created in the tracing directory when this303 Allow tracing users to take snapshot of the current buffer using the306 echo 1 > /sys/kernel/debug/tracing/snapshot[all …]
5 Description: (RW) Enable/disable tracing on this specific trace entiry.15 Description: (R) 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 …]
17 provided there are no active users and tracing is not enabled,30 there are no active users and tracing is not enabled) and then
81 b->tracing = 0; in alloc_cpu_buffers()289 cpu_buf->tracing = 1; in oprofile_begin_trace()294 cpu_buf->tracing = 0; in oprofile_end_trace()425 if (!cpu_buf->tracing) in oprofile_add_trace()440 cpu_buf->tracing = 0; in oprofile_add_trace()
17 functionality. It only supports single thread tracing currently and69 tracing for functions executed from the given function.77 and disables tracing for function executed from the given function.
60 bool "Enable tracing for RCU"66 event tracing.68 Say Y here if you want to enable RCU tracing
36 bool "Enable removal of RAM from kernel mappings for tracing"41 from the kernel mappings to be used for hardware tracing.
52 lwi $p0, [tsk+#TSK_TI_FLAGS] ! check for syscall tracing54 andi $p1, $p0, #_TIF_WORK_SYSCALL_ENTRY ! are we tracing syscalls?
1 menu "HW tracing support"
33 bool "wil6210 tracing support"39 using the kernel tracing infrastructure. Select this
