Keywords: INTERACTIVE STATISTICS THREAD PROCESS ¶ general/eventcount.stp - Interactive Count Specified Events.The script makes the information available via procfs in Prometheus readable format. The cpu_throttle.stp script monitors when CPU throttling occurs and accumulates the amount of time in milliseconds that each processor is throttled. Intel processors have hardware mechanisms that will reduce the effective processors speed to avoid exceeding set thermal or power constraints. ¶ general/cpu_throttle.stp - Monitor Intel processors for throttling due to power or thermal limits.The first parameter names the function probe points to trace. Print a timed per-thread microsecond-timed nested callgraph. ¶ general/callgraph.stp - Callgraph Tracing.The badname.stp script shows how one could prevent the creation of files with undesirable names using guru mode. ¶ general/badname.stp - Bad Filename Filter.The script prints a table showing the available attributes (bold, underline, and inverse) with color combinations for the ans_set_color() function in the ansi.stp tapset.
#Keyword file linux kernel software#
This information can be useful to determine what software is actually being used on the system. The also_ran.stp script tallies each time a executable is started or a shared library is loaded for execution. ¶ general/also_ran.stp - Keep a tally of executables run on the system.When the script exists it prints out the minimum, average, and maximum times in microseconds for each system call, followed by a count of times that each syscall was invoked and a histogram showing the distributions of times. The script tracks the wall clock time for each invocation of the system calls open, close, read, and write. ¶ general/alias_suffixes.stp - Count I/O Syscalls using Alias SuffixesĪlias_suffixes.stp is a demonstration of how alias suffixes in the systemtap language might be used.The resulting data can be analyzed to determine if there are issues with the amount of time that systemtap takes to generate instrumentation. When SystemTap completes pass 4 (compiling the instrumentation into a kernel module) the script print out the script name followed by the amount of time in milliseconds required for Pass 0 (command line option parsing), Pass 1 (script parsing), Pass 2 (elaboration), Pass 3 (code generation), and Pass 4 (module compilation). The stap_time.stp script uses the markers in SystemTap to note the amount of time that each of the passes requires. SystemTap has multiple passes to convert the text of a SystemTap script into instrumentation that actually collect data on the system. ¶ apps/stap_time.stp - Provide elapsed times for Passes of SystemTap script compilation.# stap php-trace.stp -c 'php -f hello.php'
#Keyword file linux kernel code#
Trace of executing PHP code using the enabled markers. ¶ apps/php-trace.stp - Tracing of PHP code execution.The second column is the time elapsed in microseconds between the previous and current events and the third column is the event name. The first column is microseconds since the script started. The libguestfs_log.stp script prints a log of when various libgueststartup steps are encountered. ¶ apps/libguestfs_log.stp - Trace libguestfs startup.The gmalloc_watch.stp script from Colin Walters' blog () traces the allocation of glib2 memory using the markers in glib2. ¶ apps/gmalloc_watch.stp - Tracing glib2 memory allocations.virtualization/kvm_service_time.stp - Time Statistics on KVM Exit Reasons.profiling/thread-times.stp - Profile Kernel Functions.profiling/pf4.stp - Profile Kernel/User Backtraces.profiling/linetimes.stp - Show Time Spent on Each Line of a Function.
0 kommentar(er)
