Searched refs:tracing (Results 1 – 25 of 166) sorted by relevance
1234567
4 Boot-time tracing12 Boot-time tracing allows users to trace boot-time process including17 this uses bootconfig file to describe tracing feature programming.22 Here is the list of available options list for boot time tracing in44 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 …]
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 …]
15 /sys/kernel/debug/tracing/uprobe_events, and enable it via16 /sys/kernel/debug/tracing/events/uprobes/<EVENT>/enable.21 You can also use /sys/kernel/debug/tracing/dynamic_events instead of82 /sys/kernel/debug/tracing/uprobe_profile. The first column is the filename,90 echo 'p /bin/bash:0x4245c0' > /sys/kernel/debug/tracing/uprobe_events94 echo 'r /bin/bash:0x4245c0' > /sys/kernel/debug/tracing/uprobe_events98 echo '-:p_bash_0x4245c0' >> /sys/kernel/debug/tracing/uprobe_events102 cat /sys/kernel/debug/tracing/uprobe_events106 echo > /sys/kernel/debug/tracing/uprobe_events111 # cd /sys/kernel/debug/tracing/[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:
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 …]
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
20 /sys/kernel/debug/tracing/kprobe_events, and enable it via21 /sys/kernel/debug/tracing/events/kprobes/<EVENT>/enable.23 You can also use /sys/kernel/debug/tracing/dynamic_events instead of127 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_events183 echo 'r:myretprobe do_sys_open $retval' >> /sys/kernel/debug/tracing/kprobe_events188 /sys/kernel/debug/tracing/events/kprobes/<EVENT>/format.191 cat /sys/kernel/debug/tracing/events/kprobes/myprobe/format214 echo > /sys/kernel/debug/tracing/kprobe_events[all …]
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/trigger202 tracing/error_log file. See Error Conditions in212 # cat /sys/kernel/debug/tracing/events/kmem/kmalloc/format[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 framework 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
6 tep_get_cpus, tep_set_cpus - Get / set the number of CPUs, which have a tracing21 The _tep_get_cpus()_ function gets the number of CPUs, which have a tracing24 The _tep_set_cpus()_ function sets the number of CPUs, which have a tracing26 The _cpu_ argument is the number of CPUs with tracing data.30 The _tep_get_cpus()_ functions returns the number of CPUs, which have tracing43 printf("We have tracing data for %d CPUs", tep_get_cpus(tep));
15 method tracing facility.20 ACPICA provides method tracing capability. And two functions are80 There are special log entries added by the method tracing facility at153 Note that all above method tracing facility related module parameters can163 All method tracing functions can be configured via ACPI module173 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 executing195 Disable the method tracing feature.[all …]
8 0x0001 mwavedd api tracing9 0x0002 smapi api tracing10 0x0004 3780i tracing11 0x0008 tp3780i tracing
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()
82 Adds a very slight overhead to tracing when enabled.116 # be able to offer generic tracing facilities:130 Enable the kernel tracing infrastructure.140 kernel cmdline at boot time for debugging (tracing) driver157 tracing is enabled by the administrator. If it's runtime disabled176 bool "enable/disable function tracing dynamically"181 This option will modify all the calls to function tracing190 See the files in /sys/kernel/debug/tracing:196 otherwise has native performance as long as no tracing is active.230 kernel and displays it in /sys/kernel/debug/tracing/stack_trace.[all …]
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_event291 $ cat /sys/kernel/debug/tracing/trace297 $ echo mlx5:mlx5e_delete_flower >> /sys/kernel/debug/tracing/set_event298 $ cat /sys/kernel/debug/tracing/trace304 $ echo mlx5:mlx5e_stats_flower >> /sys/kernel/debug/tracing/set_event305 $ cat /sys/kernel/debug/tracing/trace311 $ echo mlx5:mlx5e_tc_update_neigh_used_value >> /sys/kernel/debug/tracing/set_event312 $ cat /sys/kernel/debug/tracing/trace318 $ echo mlx5:mlx5e_rep_neigh_update >> /sys/kernel/debug/tracing/set_event[all …]
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()
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 …]
92 which allows tracing the instructions that a processor is executing93 This is primarily useful for instruction level tracing. Depending94 the ETM version data tracing may also be available.105 This driver provides support for the ETM4.x tracer module, tracing the107 for instruction level tracing. Depending on the implemented version108 data tracing may also be available.120 instrumentation based tracing. This is primarily used for
17 functionality. It only supports single thread tracing currently and48 Time (ms) to wait before starting tracing after program start.66 Set the size of per-cpu tracing buffer, <size> is expected to104 for the function_graph tracer only and disables tracing for function
30 bool "Enable removal of RAM from kernel mappings for tracing"34 from the kernel mappings to be used for hardware tracing.
47 bool "ath11k tracing support"50 Select this to use ath11k tracing infrastructure.
24 bool "Broadcom device tracing"30 issues. This option adds a small amount of overhead when tracing
54 lwi $p0, [tsk+#TSK_TI_FLAGS] ! check for syscall tracing56 andi $p1, $p0, #_TIF_WORK_SYSCALL_ENTRY ! are we tracing syscalls?
