FM / examples

/usr/share/systemtap/examples

Name	Size	Mode	Actions
apps/	-	0755	rm
general/	-	0755	rm
html/	-	0755	rm
interrupt/	-	0755	rm
io/	-	0755	rm
locks/	-	0755	rm
lwtools/	-	0755	rm
memory/	-	0755	rm
network/	-	0755	rm
process/	-	0755	rm
profiling/	-	0755	rm
security-band-aids/	-	0755	rm
stapgames/	-	0755	rm
virtualization/	-	0755	rm
index.html	128941	0644	edit dl rm
index.txt	75355	0644	edit dl rm
keyword-index.html	240229	0644	edit dl rm
keyword-index.txt	158357	0644	edit dl rm
metadatabase.db	194560	0644	edit dl rm
README	6178	0644	edit dl rm

Edit: /usr/share/systemtap/examples/index.html (128941B)

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">

<html>
<head>
 <title>SystemTap Examples</title>
 <link rel="stylesheet" href="html/systemtap.css" type="text/css">
 <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
 <meta http-equiv="Content-Style-Type" content="text/css">
</head>

<body>
 <table cellspacing="2" cellpadding="2" border="0" width="100%">
 <tr>
 <td valign="bottom" height="80"><img src="html/systemtaplogo.png"
 alt="SystemTap logo" width="165" height="25"></td>
 <td valign="bottom" class="topnavright" align="right">
 <a href="http://sourceware.org/systemtap/">SystemTap</a>&nbsp;|&nbsp;
 </td>
 </tr>
 </table>

<div class="mainbackground">
 <div class="maintextregion">
 <img src="html/systemtapcorner.gif">
 <table cellspacing="2" cellpadding="4" border="0" width="99%"
 style="margin-top:17;">
 <tr>
 	<td width="200">&nbsp;</td>
 	<td valign="bottom"><h1>Examples</h1></td>
 </tr>
 <tr>
 		<td>&nbsp;</td>
 		<td valign="top">

<h2>Example Indexes</h2>
		 	<ul>
 		<li><a href="index.html">All Examples</a></li>
 		<li><a href="keyword-index.html">By Keyword</a></li>
 	</ul>

For systemtap version 4.9.<h2>Best Examples</h2>
<ul>
<li><a href="#general/helloworld.stp">general/helloworld.stp - SystemTap "Hello World" Program</a></li>
<li><a href="#general/para-callgraph.stp">general/para-callgraph.stp - Callgraph Tracing with Arguments</a></li>
<li><a href="#general/varwatch.stp">general/varwatch.stp - Watch a Variable Changing Value in a Thread</a></li>
<li><a href="#general/whythefail.stp">general/whythefail.stp - Why did the function fail?</a></li>
<li><a href="#network/netfilter_summary.stp">network/netfilter_summary.stp - System-Wide Count of Network Packets by IPs</a></li>
<li><a href="#network/netfilter_summary_json.stp">network/netfilter_summary_json.stp - System-Wide Count of Network Packets by IPs</a></li>
<li><a href="#process/cycle_thief.stp">process/cycle_thief.stp - Track IRQ's and Other Processes Stealing Cycles from a Task</a></li>
<li><a href="#process/proctop.stp">process/proctop.stp - Periodically Print Process Information With History</a></li>
<li><a href="#process/strace.stp">process/strace.stp - Trace system calls</a></li>
<li><a href="#process/thread-business.stp">process/thread-business.stp - monitor syscall history</a></li>
<li><a href="#profiling/fntimes.stp">profiling/fntimes.stp - Show Functions Taking Longer Than Usual</a></li>
<li><a href="#profiling/latencytap.stp">profiling/latencytap.stp - Show Reasons and Durations for Processes Sleeping</a></li>
<li><a href="#profiling/linetimes.stp">profiling/linetimes.stp - Show Time Spent on Each Line of a Function</a></li>
<li><a href="#profiling/pf4.stp">profiling/pf4.stp - Profile Kernel/User Backtraces</a></li>
<li><a href="#profiling/thread-times.stp">profiling/thread-times.stp - Profile Kernel Functions</a></li>
<li><a href="#stapgames/2048.stp">stapgames/2048.stp - 2048</a></li>
<li><a href="#virtualization/kvm_service_time.stp">virtualization/kvm_service_time.stp - Time Statistics on KVM Exit Reasons</a></li>
</ul>

<h2>All 194 Examples</h2>
<ul>
<li><a name="apps/gmalloc_watch.stp"></a><a href="#apps/gmalloc_watch.stp">&para;</a> <a href="apps/gmalloc_watch.stp">apps/gmalloc_watch.stp</a> - Tracing glib2 memory allocations 
keywords: <a href="keyword-index.html#TRACE">TRACE</a> 
The gmalloc_watch.stp script from Colin Walters&#39; blog (https://blog.verbum.org/2011/03/19/analyzing-memory-use-with-systemtap/) traces the allocation of glib2 memory using the markers in glib2.<pre># stap gmalloc_watch.stp -T 1</pre>
</li><li><a name="apps/libguestfs_log.stp"></a><a href="#apps/libguestfs_log.stp">&para;</a> <a href="apps/libguestfs_log.stp">apps/libguestfs_log.stp</a> - Trace libguestfs startup 
keywords: <a href="keyword-index.html#APPLICATION">APPLICATION</a> <a href="keyword-index.html#TRACE">TRACE</a> <a href="keyword-index.html#BPF">BPF</a> 
The libguestfs_log.stp script prints a log of when various libgueststartup steps are encountered. The first column is microseconds since the script started. The second column is the time elapsed in microseconds between the previous and current events and the third column is the event name.<pre># stap libguestfs_log.stp -T 1</pre>
</li><li><a name="apps/php-trace.stp"></a><a href="#apps/php-trace.stp">&para;</a> <a href="apps/php-trace.stp">apps/php-trace.stp</a> - Tracing of PHP code execution 
keywords: <a href="keyword-index.html#TRACE">TRACE</a> <a href="keyword-index.html#DYNINST">DYNINST</a> 
Trace of executing PHP code using the enabled markers.<pre># stap php-trace.stp -c &#39;php -f hello.php&#39;</pre>
</li><li><a name="apps/stap_time.stp"></a><a href="#apps/stap_time.stp">&para;</a> <a href="apps/stap_time.stp">apps/stap_time.stp</a> - Provide elapsed times for Passes of SystemTap script compilation 
keywords: <a href="keyword-index.html#APPLICATION">APPLICATION</a> <a href="keyword-index.html#TRACE">TRACE</a> 
SystemTap has multiple passes to convert the text of a SystemTap script into instrumentation that actually collect data on the system. The stap_time.stp script uses the markers in SystemTap to note the amount of time that each of the passes requires. 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 resulting data can be analyzed to determine if there are issues with the amount of time that systemtap takes to generate instrumentation.<pre># stap stap_time.stp -T 1</pre>
</li><li><a name="general/alias_suffixes.stp"></a><a href="#general/alias_suffixes.stp">&para;</a> <a href="general/alias_suffixes.stp">general/alias_suffixes.stp</a> - Count I/O Syscalls using Alias Suffixes 
keywords: <a href="keyword-index.html#IO">IO</a> <a href="keyword-index.html#STATISTICS">STATISTICS</a> 
alias_suffixes.stp is a demonstration of how alias suffixes in the systemtap language might be used. The script tracks the wall clock time for each invocation of the system calls open, close, read, and write. 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.<pre># stap alias_suffixes.stp -T 1</pre>
</li><li><a name="general/also_ran.stp"></a><a href="#general/also_ran.stp">&para;</a> <a href="general/also_ran.stp">general/also_ran.stp</a> - Keep a tally of executables run on the system 
keywords: <a href="keyword-index.html#PROMETHEUS">PROMETHEUS</a> 
The also_ran.stp script tallies each time a executable is started or a shared library is loaded for execution. This information can be useful to determine what software is actually being used on the system. The script makes the information available via procfs in Prometheus readable format.<pre># stap also_ran.stp -T 1</pre>
</li><li><a name="general/ansi_colors.stp"></a><a href="#general/ansi_colors.stp">&para;</a> <a href="general/ansi_colors.stp">general/ansi_colors.stp</a> - Color Table for ansi_set_color() 
keywords: <a href="keyword-index.html#FORMAT">FORMAT</a> <a href="keyword-index.html#BPF">BPF</a> 
The script prints a table showing the available color combinations for the ansi_set_color() function in the ansi.stp tapset.<pre># stap ansi_colors.stp</pre>
</li><li><a name="general/ansi_colors2.stp"></a><a href="#general/ansi_colors2.stp">&para;</a> <a href="general/ansi_colors2.stp">general/ansi_colors2.stp</a> - Show Attribues in Table for ansi_set_color() 
keywords: <a href="keyword-index.html#FORMAT">FORMAT</a> <a href="keyword-index.html#BPF">BPF</a> 
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.<pre># stap ansi_colors2.stp</pre>
</li><li><a name="general/badname.stp"></a><a href="#general/badname.stp">&para;</a> <a href="general/badname.stp">general/badname.stp</a> - Bad Filename Filter 
keywords: <a href="keyword-index.html#FILESYSTEM">FILESYSTEM</a> <a href="keyword-index.html#GURU">GURU</a> 
The badname.stp script shows how one could prevent the creation of files with undesirable names using guru mode.<a href="general/badname.txt">sample usage in general/badname.txt
</li><li><a name="general/callgraph.stp"></a><a href="#general/callgraph.stp">&para;</a> <a href="general/callgraph.stp">general/callgraph.stp</a> - Callgraph Tracing 
keywords: <a href="keyword-index.html#SIMPLE">SIMPLE</a> <a href="keyword-index.html#TRACE">TRACE</a> <a href="keyword-index.html#CALLGRAPH">CALLGRAPH</a> 
Print a timed per-thread microsecond-timed nested callgraph. The first parameter names the function probe points to trace.<a href="general/callgraph.txt">sample usage in general/callgraph.txt
</li><li><a name="general/cpu_throttle.stp"></a><a href="#general/cpu_throttle.stp">&para;</a> <a href="general/cpu_throttle.stp">general/cpu_throttle.stp</a> - Monitor Intel processors for throttling due to power or thermal limits 
keywords: <a href="keyword-index.html#PROMETHEUS">PROMETHEUS</a> <a href="keyword-index.html#LIMITS">LIMITS</a> 
Intel processors have hardware mechanisms that will reduce the effective processors speed to avoid exceeding set thermal or power constraints. The cpu_throttle.stp script monitors when CPU throttling occurs and accumulates the amount of time in milliseconds that each processor is throttled. The script makes the information available via procfs in Prometheus readable format.<pre># stap cpu_throttle.stp -T 1</pre>
</li><li><a name="general/eventcount.stp"></a><a href="#general/eventcount.stp">&para;</a> <a href="general/eventcount.stp">general/eventcount.stp</a> - Interactive Count Specified Events 
keywords: <a href="keyword-index.html#INTERACTIVE">INTERACTIVE</a> <a href="keyword-index.html#STATISTICS">STATISTICS</a> <a href="keyword-index.html#THREAD">THREAD</a> <a href="keyword-index.html#PROCESS">PROCESS</a> 
The script periodically prints a count of specified events and their related tid&#39;s over the course of execution. Numerous configuration options exist to control filtering / reporting, some of which can be modified at runtime. See the script source for more information.<a href="general/eventcount.txt">sample usage in general/eventcount.txt
</li><li><a name="general/floatingpoint.stp"></a><a href="#general/floatingpoint.stp">&para;</a> <a href="general/floatingpoint.stp">general/floatingpoint.stp</a> - SystemTap "Floating Point" Program 
keywords: <a href="keyword-index.html#SIMPLE">SIMPLE</a> <a href="keyword-index.html#FLOATINGPOINT">FLOATINGPOINT</a> 
A basic &quot;Floating Point&quot; program implemented in SystemTap script. It extracts floating point from benchmark-sdt section in main.cxx and takes one pseudo floating point, printing out results of various simple floating point operations.<a href="general/floatingpoint.txt">sample usage in general/floatingpoint.txt
</li><li><a name="general/func_time_stats.stp"></a><a href="#general/func_time_stats.stp">&para;</a> <a href="general/func_time_stats.stp">general/func_time_stats.stp</a> - Function Time Statistics 
keywords: <a href="keyword-index.html#FUNCTION">FUNCTION</a> <a href="keyword-index.html#STATISTICS">STATISTICS</a> 
The func_time_stats.stp script tracks the wall clock time for each invocation of the function probe listed as the first command line argument. When the script exits it prints out the minimum, average, and maximum times in microseconds followed by a count of times that the function was called and a histogram showing the distributions of times.<a href="general/func_time_stats.txt">sample usage in general/func_time_stats.txt
</li><li><a name="general/graphs.stp"></a><a href="#general/graphs.stp">&para;</a> <a href="general/graphs.stp">general/graphs.stp</a> - Graphing Disk and CPU Utilization with gnuplot 
keywords: <a href="keyword-index.html#MONITORING">MONITORING</a> 
The script tracks the disk and CPU utilization. It prints a stream of data which, when piped directly into gnuplot, draws historical curves for each.<pre># stap graphs.stp -T 1</pre>
</li><li><a name="general/helloworld.stp"></a><a href="#general/helloworld.stp">&para;</a> <a href="general/helloworld.stp">general/helloworld.stp</a> - SystemTap "Hello World" Program 
keywords: <a href="keyword-index.html#_BEST">_BEST</a> <a href="keyword-index.html#SIMPLE">SIMPLE</a> <a href="keyword-index.html#BPF">BPF</a> 
A basic &quot;Hello World&quot; program implemented in SystemTap script. It prints out &quot;hello world&quot; message and then immediately exits.<pre># stap helloworld.stp</pre>
</li><li><a name="general/key.stp"></a><a href="#general/key.stp">&para;</a> <a href="general/key.stp">general/key.stp</a> - make keyboard noises 
keywords: <a href="keyword-index.html#SIMPLE">SIMPLE</a> 
For fans of Leroy Anderson and Typewriters only, this script arranges to play a click or a zing for various keystrokes.<pre># stap key.stp -c &#39;sleep 5&#39;</pre>
</li><li><a name="general/keyhack.stp"></a><a href="#general/keyhack.stp">&para;</a> <a href="general/keyhack.stp">general/keyhack.stp</a> - Hack the keyboard 
keywords: <a href="keyword-index.html#SIMPLE">SIMPLE</a> <a href="keyword-index.html#GURU">GURU</a> 
This script makes it appear that one&#39;s keyboard is broken, by changing keycodes at the kernel device driver level. Annoy your friends!<pre># stap -g keyhack.stp -c &#39;sleep 5&#39;</pre>
</li><li><a name="general/measureinterval.stp"></a><a href="#general/measureinterval.stp">&para;</a> <a href="general/measureinterval.stp">general/measureinterval.stp</a> - Measure intervals between events 
keywords: <a href="keyword-index.html#MONITORING">MONITORING</a> 
The measureinteval.stp script allows quick creation of instrumentation to measure quantity between different probe points, aggregate the measurements, and display the results. The first argument to the script is the quantity to measure such as time in microseconds via &quot;gettimeofday_us()&quot;. There could be multiple intervals being measured concurrently and the second argument is the means to match the start probe points listed in the fourth argument with the end probes listed in the fifth argument. The third argument is how to display the aggregated data. The data could be displayed as a sum (@sum), an average (@avg), or a histogram (@hist_log). The fourth and fifth arguments are lists of probes marking the start and end of an interval. An optional sixth argument allows grouping of the intervals. One could use &quot;tid()&quot; for the matching argument to measure the intervals on a per-thread basis, but then use &quot;execname()&quot; for the optional argument to group the measurements by executable name. If there is no sixth argument, all the intervals are aggregated into a single entry.<pre># stap measureinterval.stp &quot;gettimeofday_us()&quot; &quot;tid()&quot; @sum vm.pagefault \
vm.pagefault.return &quot;execname()&quot; -c &#39;sleep 3&#39;</pre>
</li><li><a name="general/para-callgraph-verbose.stp"></a><a href="#general/para-callgraph-verbose.stp">&para;</a> <a href="general/para-callgraph-verbose.stp">general/para-callgraph-verbose.stp</a> - Callgraph Tracing with Verbose Arguments 
keywords: <a href="keyword-index.html#TRACE">TRACE</a> <a href="keyword-index.html#CALLGRAPH">CALLGRAPH</a> 
Print a timed per-thread microsecond-timed callgraph, complete with pretty-printed function parameters and return values. The first parameter names the function probe points to trace. The optional second parameter names the probe points for trigger functions, which acts to enable tracing for only those functions that occur while the current thread is nested within the trigger.<pre># stap para-callgraph-verbose.stp &#39;kernel.function(&quot;*@fs/proc*.c&quot;)&#39; \
&#39;kernel.function(&quot;vfs_read&quot;)&#39; -c &quot;cat /proc/sys/vm/* || true&quot;</pre>
</li><li><a name="general/para-callgraph.stp"></a><a href="#general/para-callgraph.stp">&para;</a> <a href="general/para-callgraph.stp">general/para-callgraph.stp</a> - Callgraph Tracing with Arguments 
keywords: <a href="keyword-index.html#_BEST">_BEST</a> <a href="keyword-index.html#TRACE">TRACE</a> <a href="keyword-index.html#CALLGRAPH">CALLGRAPH</a> 
Print a timed per-thread microsecond-timed callgraph, complete with function parameters and return values. The first parameter names the function probe points to trace. The optional second parameter names the probe points for trigger functions, which acts to enable tracing for only those functions that occur while the current thread is nested within the trigger.<a href="general/para-callgraph.txt">sample usage in general/para-callgraph.txt
</li><li><a name="general/pyexample.stp"></a><a href="#general/pyexample.stp">&para;</a> <a href="general/pyexample.stp">general/pyexample.stp</a> - SystemTap python 2 support tapset 
keywords: <a href="keyword-index.html#SIMPLE">SIMPLE</a> 
A python support tapset that displays backtraces and variable values<pre># PYTHONPATH=$PYEXECDIR stap -g --suppress-time-limits -c \
&#39;/usr/bin/python3 -m HelperSDT pyexample.py 35&#39; pyexample.stp python2</pre>
</li><li><a name="general/pyexample.stp"></a><a href="#general/pyexample.stp">&para;</a> <a href="general/pyexample.stp">general/pyexample.stp</a> - SystemTap python 3 support tapset 
keywords: <a href="keyword-index.html#SIMPLE">SIMPLE</a> 
A python support tapset that displays backtraces and variable values<pre># PYTHONPATH=$PY3EXECDIR stap -g --suppress-time-limits -c \
&#39;/usr/bin/python3 -m HelperSDT pyexample.py 35&#39; pyexample.stp python3</pre>
</li><li><a name="general/regex.stp"></a><a href="#general/regex.stp">&para;</a> <a href="general/regex.stp">general/regex.stp</a> - Report opened files whose names match a given regex 
keywords: <a href="keyword-index.html#REGEX">REGEX</a> 
Uses the regex functionality to detect opened files whose names match a pattern given on the command line. If no command line parameter is given, demonstrate by filtering for files that end with an extension showing them to be an archive.<pre># stap regex.stp -T 1</pre>
</li><li><a name="general/sizeof.stp"></a><a href="#general/sizeof.stp">&para;</a> <a href="general/sizeof.stp">general/sizeof.stp</a> - Print the Size of a C Type 
keywords: <a href="keyword-index.html#STATISTICS">STATISTICS</a> <a href="keyword-index.html#MEMORY">MEMORY</a> <a href="keyword-index.html#BPF">BPF</a> 
This script prints the size of a type, based on dwarf debuginfo for any kernel or userspace module, or trial-compilation of a given header file name.<a href="general/sizeof.txt">sample usage in general/sizeof.txt
</li><li><a name="general/sizeof_interactive.stp"></a><a href="#general/sizeof_interactive.stp">&para;</a> <a href="general/sizeof_interactive.stp">general/sizeof_interactive.stp</a> - Interactive Print the Size of a C Type 
keywords: <a href="keyword-index.html#STATISTICS">STATISTICS</a> <a href="keyword-index.html#MEMORY">MEMORY</a> <a href="keyword-index.html#INTERACTIVE">INTERACTIVE</a> 
This script prints the size of a type, based on dwarf debuginfo for any kernel or userspace module, or trial-compilation of a given header file name. Types and corresponding locations are provided to the script at runtime via keyboard input. The format of the input is identical to that of sizeof.stp (see script source for more information). Types and locations can be repeatedly given until the process is terminated. <a href="general/sizeof_interactive.txt">sample usage in general/sizeof_interactive.txt
</li><li><a name="general/socket-events.stp"></a><a href="#general/socket-events.stp">&para;</a> <a href="general/socket-events.stp">general/socket-events.stp</a> - Trace Socket Activity of a Process 
keywords: <a href="keyword-index.html#SOCKET">SOCKET</a> <a href="keyword-index.html#SYSCALL">SYSCALL</a> 
Prints the life cycle of all sockets associated with a process. This includes bytes and timing. The timing information that is tracked includes event completion relative to the start of said event and the end of the previous event. Currently tracks read, write, recv, send, connect and close.<pre># stap socket-events.stp</pre>
</li><li><a name="general/stopwatches.stp"></a><a href="#general/stopwatches.stp">&para;</a> <a href="general/stopwatches.stp">general/stopwatches.stp</a> - See the amount of wall clock time a process spends in various states 
keywords: <a href="keyword-index.html#TIME">TIME</a> <a href="keyword-index.html#BPF">BPF</a> 
The stopwatch.stp script illustrates how to use multiple stopwatches record how much wallclock time a process spends in kernel- and user-space. On exit the script prints out the time in seconds, milliseconds, microseconds, and nanoseconds. Note that this output of this script is not directly comparable to the time command because time records the time that the process is actually active in kernel- and user-space.<pre># stap stopwatches.stp -T 1</pre>
</li><li><a name="general/tcl-funtop.stp"></a><a href="#general/tcl-funtop.stp">&para;</a> <a href="general/tcl-funtop.stp">general/tcl-funtop.stp</a> - Profile Tcl calls 
keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> 
The tcl-funtop.stp script displays a top-like view of most frequently used Tcl functions for the each five second interval.<pre># stap tcl-funtop.stp -T 5</pre>
</li><li><a name="general/tcl-trace.stp"></a><a href="#general/tcl-trace.stp">&para;</a> <a href="general/tcl-trace.stp">general/tcl-trace.stp</a> - Callgraph Tracing of Tcl code 
keywords: <a href="keyword-index.html#CALLGRAPH">CALLGRAPH</a> 
Print a timed per-thread microsecond-timed callgraph of executing Tcl code.<pre># stap tcl-trace.stp -T 5</pre>
</li><li><a name="general/varwatch.stp"></a><a href="#general/varwatch.stp">&para;</a> <a href="general/varwatch.stp">general/varwatch.stp</a> - Watch a Variable Changing Value in a Thread 
keywords: <a href="keyword-index.html#_BEST">_BEST</a> <a href="keyword-index.html#MONITORING">MONITORING</a> 
This script places a set of probes (specified by $1), each of which monitors the state of some context $variable expression (specified by $2). Whenever the value changes, with respect to the active thread, the event is traced.<a href="general/varwatch.txt">sample usage in general/varwatch.txt
</li><li><a name="general/watchdog.stp"></a><a href="#general/watchdog.stp">&para;</a> <a href="general/watchdog.stp">general/watchdog.stp</a> - Watchdog Timer for Arbitrary Events 
keywords: <a href="keyword-index.html#WATCHDOG">WATCHDOG</a> <a href="keyword-index.html#BACKTRACE">BACKTRACE</a> 
The watchdog.stp script provides a watchdog timer mechanism for arbitrary events. The script takes three arguments: the events to start watchdog timer, the event to stop the watchdog timer, and the time in millseconds for the watchdog. If the watchdog timer is exceed, the script will trigger a stack backtrace of the user-process that timed out using pstack. This script can be used to diagnose what the userspace application is doing when a slower than expected operation occurs.<pre># stap watchdog.stp &#39;syscall.nanosleep&#39; &#39;syscall.nanosleep.return&#39; 1000 \
-T 1</pre>
</li><li><a name="general/whythefail.stp"></a><a href="#general/whythefail.stp">&para;</a> <a href="general/whythefail.stp">general/whythefail.stp</a> - Why did the function fail? 
keywords: <a href="keyword-index.html#SPECULATION">SPECULATION</a> <a href="keyword-index.html#MONITORING">MONITORING</a> <a href="keyword-index.html#FUNCTION">FUNCTION</a> <a href="keyword-index.html#TRACE">TRACE</a> <a href="keyword-index.html#_BEST">_BEST</a> 
The whythefail.stp script prints a statement-execution trace for a given function, but only for those runs of the function that ended up with a (configurable) post-return condition.<a href="general/whythefail.txt">sample usage in general/whythefail.txt
</li><li><a name="interrupt/interrupts-by-dev.stp"></a><a href="#interrupt/interrupts-by-dev.stp">&para;</a> <a href="interrupt/interrupts-by-dev.stp">interrupt/interrupts-by-dev.stp</a> - Record Interrupts on a Per-Device Basis 
keywords: <a href="keyword-index.html#INTERRUPT">INTERRUPT</a> 
The interrupts-by-dev.stp script profiles interrupts received by each device per 100 ms.<a href="interrupt/interrupts-by-dev.txt">sample usage in interrupt/interrupts-by-dev.txt
</li><li><a name="interrupt/scf.stp"></a><a href="#interrupt/scf.stp">&para;</a> <a href="interrupt/scf.stp">interrupt/scf.stp</a> - Tally Backtraces for Inter-Processor Interrupt 
keywords: <a href="keyword-index.html#INTERRUPT">INTERRUPT</a> <a href="keyword-index.html#BACKTRACE">BACKTRACE</a> 
The Linux kernel function smp_call_function causes expensive inter-processor interrupts (IPIs). The scf.stp script tallies the processes and backtraces causing the interprocessor interrupts to identify the cause of the expensive IPI. On exit the script prints the tallies in descending frequency.<pre># stap scf.stp -T 1</pre>
</li><li><a name="io/capture_ssl_master_secrets.stp"></a><a href="#io/capture_ssl_master_secrets.stp">&para;</a> <a href="io/capture_ssl_master_secrets.stp">io/capture_ssl_master_secrets.stp</a> - Capture SSL/TLS master secrets from gnutls and openssl users 
keywords: <a href="keyword-index.html#IO">IO</a> <a href="keyword-index.html#MONITORING">MONITORING</a> 
Capture SSL/TLS master secrets from gnutls and openssl users for easy traffic decryption<a href="io/capture_ssl_master_secrets.txt">sample usage in io/capture_ssl_master_secrets.txt
</li><li><a name="io/deviceseeks.stp"></a><a href="#io/deviceseeks.stp">&para;</a> <a href="io/deviceseeks.stp">io/deviceseeks.stp</a> - Histograms of Seek Behavior for Each Device 
keywords: <a href="keyword-index.html#DISK">DISK</a> 
The deviceseeks.stp script generates a periodic histogram showing the frequency of different sized seeks (in sectors) on each device, or optional given device-name regexp<a href="io/deviceseeks.txt">sample usage in io/deviceseeks.txt
</li><li><a name="io/disktop.stp"></a><a href="#io/disktop.stp">&para;</a> <a href="io/disktop.stp">io/disktop.stp</a> - Summarize Disk Read/Write Traffic 
keywords: <a href="keyword-index.html#DISK">DISK</a> 
Get the status of reading/writing disk every 5 seconds, output top ten entries during that period.<pre># stap disktop.stp -T 1</pre>
</li><li><a name="io/eatmydata.stp"></a><a href="#io/eatmydata.stp">&para;</a> <a href="io/eatmydata.stp">io/eatmydata.stp</a> - disable fsync 
keywords: <a href="keyword-index.html#IO">IO</a> <a href="keyword-index.html#GURU">GURU</a> <a href="keyword-index.html#SIMPLE">SIMPLE</a> 
Suppresses fsync() syscalls from processes identified by stap -c/-x by turning them into presumed-faster fsync() on some dummy or other file descriptor<a href="io/eatmydata.txt">sample usage in io/eatmydata.txt
</li><li><a name="io/enospc.stp"></a><a href="#io/enospc.stp">&para;</a> <a href="io/enospc.stp">io/enospc.stp</a> - Report an disk out-of-space condition. 
keywords: <a href="keyword-index.html#DISK">DISK</a> <a href="keyword-index.html#FILESYSTEM">FILESYSTEM</a> 
This script monitors a filesystem implementations for early internal indications of ENOSPC, and reports these to the system logger and the systemtap console.<pre># stap enospc.stp -T 1</pre>
</li><li><a name="io/inodewatch.stp"></a><a href="#io/inodewatch.stp">&para;</a> <a href="io/inodewatch.stp">io/inodewatch.stp</a> - Monitoring Reads and Writes to a File 
keywords: <a href="keyword-index.html#IO">IO</a> 
 The inodewatch.stp outputs the executable name and process id each time a read or write occurs to the specified inode on the specified major/minor device.<pre># stap inodewatch.stp 0x08 0x01 100 -T 1</pre>
</li><li><a name="io/inodewatch2.stp"></a><a href="#io/inodewatch2.stp">&para;</a> <a href="io/inodewatch2.stp">io/inodewatch2.stp</a> - Monitoring Attribute Changes to a File 
keywords: <a href="keyword-index.html#IO">IO</a> 
 The inodewatch2.stp script outputs the executable name, process id, and attributes each time the attributes are changed on the specified inode on the specified major/minor device.<pre># stap inodewatch2.stp 0x08 0x01 100 -T 1</pre>
</li><li><a name="io/io_submit.stp"></a><a href="#io/io_submit.stp">&para;</a> <a href="io/io_submit.stp">io/io_submit.stp</a> - Tally Reschedule Reason During AIO io_submit Call 
keywords: <a href="keyword-index.html#IO">IO</a> <a href="keyword-index.html#BACKTRACE">BACKTRACE</a> 
When a reschedule occurs during an AIO io_submit call, accumulate the traceback in a histogram. When the script exits prints out a sorted list from most common to least common backtrace.<pre># stap io_submit.stp -T 1</pre>
</li><li><a name="io/ioblktime.stp"></a><a href="#io/ioblktime.stp">&para;</a> <a href="io/ioblktime.stp">io/ioblktime.stp</a> - Average Time Block IO Requests Spend in Queue 
keywords: <a href="keyword-index.html#IO">IO</a> 
The ioblktime.stp script tracks the amount of time that each block IO requests spend waiting for completion. The script computes the average waiting time for block IO per device and prints list every 10 seconds. In some cases there can be too many outstanding block IO operations and the script may exceed the default number of MAXMAPENTRIES allowed. In this case the allowed number can be increased with &quot;-DMAXMAPENTRIES=10000&quot; option on the stap command line.<pre># stap ioblktime.stp -T 1</pre>
</li><li><a name="io/iodevstats.stp"></a><a href="#io/iodevstats.stp">&para;</a> <a href="io/iodevstats.stp">io/iodevstats.stp</a> - List Executables Reading and Writing the Most Data by Device 
keywords: <a href="keyword-index.html#IO">IO</a> <a href="keyword-index.html#PROFILING">PROFILING</a> 
 The iodevstats.stp script measures the amount of data successfully read and written by all the executables for each io device on the system. The output is sorted from greatest sum of bytes read and written to a device by an executable to the least. The output contains device major/minor number, the count of operations (reads and writes), the totals and averages for the number of bytes read and written.<a href="io/iodevstats.txt">sample usage in io/iodevstats.txt
</li><li><a name="io/iostat-scsi.stp"></a><a href="#io/iostat-scsi.stp">&para;</a> <a href="io/iostat-scsi.stp">io/iostat-scsi.stp</a> - IO Statistics for SCSI Devices 
keywords: <a href="keyword-index.html#IO">IO</a> <a href="keyword-index.html#PROFILING">PROFILING</a> <a href="keyword-index.html#SCSI">SCSI</a> 
The iostat-scsi.stp script provides a breakdown of the number of blks read and written on the machine&#39;s various SCSI devices. The script takes one argument which is the number of seconds between reports.<a href="io/iostat-scsi.txt">sample usage in io/iostat-scsi.txt
</li><li><a name="io/iostats.stp"></a><a href="#io/iostats.stp">&para;</a> <a href="io/iostats.stp">io/iostats.stp</a> - List Executables Reading and Writing the Most Data 
keywords: <a href="keyword-index.html#IO">IO</a> <a href="keyword-index.html#PROFILING">PROFILING</a> 
 The iostat.stp script measures the amount of data successfully read and written by all the executables on the system. The output is sorted from most greatest sum of bytes read and written by an executable to the least. The output contains the count of operations (opens, reads, and writes), the totals and averages for the number of bytes read and written.<a href="io/iostats.txt">sample usage in io/iostats.txt
</li><li><a name="io/iotime.stp"></a><a href="#io/iotime.stp">&para;</a> <a href="io/iotime.stp">io/iotime.stp</a> - Trace Time Spent in Read and Write for Files 
keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> <a href="keyword-index.html#SYSCALL">SYSCALL</a> <a href="keyword-index.html#IO">IO</a> <a href="keyword-index.html#FILE">FILE</a> 
The script watches each open, close, read, and write syscalls on the system. For each file the scripts observes opened it accumulates the amount of wall clock time spent in read and write operations and the number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in parentheses. The first line with the &quot;access&quot; keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the &quot;iotime&quot; keyword list the file name and the number of microseconds accumulated in the read and write syscalls.<pre># stap iotime.stp -T 1</pre>
</li><li><a name="io/iotop.stp"></a><a href="#io/iotop.stp">&para;</a> <a href="io/iotop.stp">io/iotop.stp</a> - Periodically Print IO Activity by Process Name 
keywords: <a href="keyword-index.html#IO">IO</a> 
Every five seconds print out the top ten executables generating I/O traffic during that interval sorted in descending order.<pre># stap iotop.stp -T 1</pre>
</li><li><a name="io/mbrwatch.stp"></a><a href="#io/mbrwatch.stp">&para;</a> <a href="io/mbrwatch.stp">io/mbrwatch.stp</a> - Monitor Read/Write of the Boot Sector Area of Block Devices 
keywords: <a href="keyword-index.html#IO">IO</a> <a href="keyword-index.html#MONITORING">MONITORING</a> <a href="keyword-index.html#DISK">DISK</a> <a href="keyword-index.html#SIMPLE">SIMPLE</a> 
 The mbrwatch.stp script reports any attempted reads/writes of the first few sectors of a raw block device.<a href="io/mbrwatch.txt">sample usage in io/mbrwatch.txt
</li><li><a name="io/nfs_func_users.stp"></a><a href="#io/nfs_func_users.stp">&para;</a> <a href="io/nfs_func_users.stp">io/nfs_func_users.stp</a> - Tally the Number of NFS Functions Used by Each Process 
keywords: <a href="keyword-index.html#IO">IO</a> <a href="keyword-index.html#PROFILING">PROFILING</a> 
The nfs_func_users.stp script counts the uses of NFS functions in the kernel on a per process bases. The output is sorted from the process with the greatest number of NFS functions called to the least. The output contains the executable name, the process number, and the total number of NFS functions called by the process.<pre># stap nfs_func_users.stp -T 1</pre>
</li><li><a name="io/slowvfs.stp"></a><a href="#io/slowvfs.stp">&para;</a> <a href="io/slowvfs.stp">io/slowvfs.stp</a> - Trace slow vfs opens. 
keywords: <a href="keyword-index.html#IO">IO</a> <a href="keyword-index.html#SIMPLE">SIMPLE</a> 
This script prints a line for every kernel vfs_open operation that takes longer than a configurable number of microseconds. Highly contended or remote filesystems are likelier to hit this.<pre># stap slowvfs.stp -G sloth=10 -c &#39;find /proc &gt;/dev/null || true&#39;</pre>
</li><li><a name="io/switchfile.stp"></a><a href="#io/switchfile.stp">&para;</a> <a href="io/switchfile.stp">io/switchfile.stp</a> - Switch log files 
keywords: <a href="keyword-index.html#IO">IO</a> 
Every second print a log message and switch log files every 5 seconds.<pre># stap -o /tmp/switchfile.stp.out switchfile.stp -T 8</pre>
</li><li><a name="io/traceaio.stp"></a><a href="#io/traceaio.stp">&para;</a> <a href="io/traceaio.stp">io/traceaio.stp</a> - Trace calls to io_submit 
keywords: <a href="keyword-index.html#IO">IO</a> 
Trace calls to io_submit, logging iocbs and iovecs.<a href="io/traceaio.txt">sample usage in io/traceaio.txt
</li><li><a name="io/traceio.stp"></a><a href="#io/traceio.stp">&para;</a> <a href="io/traceio.stp">io/traceio.stp</a> - Track Cumulative IO Activity by Process Name 
keywords: <a href="keyword-index.html#IO">IO</a> 
Every second print out the top ten executables sorted in descending order based on cumulative I/O traffic observed.<pre># stap traceio.stp -T 1</pre>
</li><li><a name="io/traceio2.stp"></a><a href="#io/traceio2.stp">&para;</a> <a href="io/traceio2.stp">io/traceio2.stp</a> - Watch IO Activity on a Particular Device 
keywords: <a href="keyword-index.html#IO">IO</a> 
Print out the executable name and process number as reads and writes to the specified device occur.<pre># stap traceio2.stp 0x0801 -T 1</pre>
</li><li><a name="io/ttyspy.stp"></a><a href="#io/ttyspy.stp">&para;</a> <a href="io/ttyspy.stp">io/ttyspy.stp</a> - Monitor TTY Typing 
keywords: <a href="keyword-index.html#IO">IO</a> <a href="keyword-index.html#TTY">TTY</a> <a href="keyword-index.html#MONITORING">MONITORING</a> <a href="keyword-index.html#GURU">GURU</a> 
The ttyspy.stp script uses tty_audit hooks to monitor recent typing activity on the system, printing a scrolling record of recent keystrokes, on a per-tty basis.<a href="io/ttyspy.txt">sample usage in io/ttyspy.txt
</li><li><a name="locks/bkl.stp"></a><a href="#locks/bkl.stp">&para;</a> <a href="locks/bkl.stp">locks/bkl.stp</a> - Tracing Contention on Big Kernel Lock 
keywords: <a href="keyword-index.html#LOCKING">LOCKING</a> 
The bkl.stp script can help determine whether the Big Kernel Lock (BKL) is causing serialization on a multiprocessor system due to excessive contention of the BKL. The bkl.stp script takes two arguments. The first one is optional, and used to enable backtraces, and print them once a process has been holding the BKL for a user specified number of nseconds is reached. The second option is compulsory and is the number of processes waiting for the Big Kernel Lock (BKL). When the number of processes waiting for the BKL is reached or exceeded, the script will print a time stamp, the number of processes waiting for the BKL, the holder of the BKL, and the amount of time the BKL was held. If backtraces are enabled, a backtrace will be printed as well.<pre># stap bkl.stp -T 1 1</pre>
</li><li><a name="locks/bkl_stats.stp"></a><a href="#locks/bkl_stats.stp">&para;</a> <a href="locks/bkl_stats.stp">locks/bkl_stats.stp</a> - Per Process Statistics on Big Kernel Lock Use 
keywords: <a href="keyword-index.html#LOCKING">LOCKING</a> 
The bkl_stats.stp script can indicate which processes have excessive waits for the Big Kernel Lock (BKL) and which processes are taking the BKL for long periods of time. The bkl_stats.stp script prints lists of all the processes that require the BKL. Every five seconds two tables are printed out. The first table lists the processes that waited for the BKL followed by the number of times that the process waited, the minimum time of the wait, the average and the maximum time waited. The second table lists has similar information for the time spent in holding the lock for each of the processes.<pre># stap bkl_stats.stp -T 1</pre>
</li><li><a name="lwtools/accept2close-nd.stp"></a><a href="#lwtools/accept2close-nd.stp">&para;</a> <a href="lwtools/accept2close-nd.stp">lwtools/accept2close-nd.stp</a> - Show socket lifespan, from accept() to close() (non-debuginfo) 
keywords: <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#SOCKET">SOCKET</a> 
This traces socket duration from the accept() syscall to close(), and provides details on the lifespan of these passive connections, showing the distribution as a histogram.<a href="lwtools/accept2close-nd.txt">sample usage in lwtools/accept2close-nd.txt
</li><li><a name="lwtools/biolatency-nd.stp"></a><a href="#lwtools/biolatency-nd.stp">&para;</a> <a href="lwtools/biolatency-nd.stp">lwtools/biolatency-nd.stp</a> - Measure block I/O latency distribution (non-debuginfo) 
keywords: <a href="keyword-index.html#IO">IO</a> 
This measures block I/O latency (storage I/O, ie, disk I/O), and shows the distribution as a histogram. This can be useful to identify the characteristics of I/O latency, beyond the averages shown by iostat(1). For example, to study I/O latency outliers, or multi-modal distributions.<pre># stap biolatency-nd.stp 1 1</pre>
</li><li><a name="lwtools/bitesize-nd.stp"></a><a href="#lwtools/bitesize-nd.stp">&para;</a> <a href="lwtools/bitesize-nd.stp">lwtools/bitesize-nd.stp</a> - Measure block I/O size distribution (non-debuginfo) 
keywords: <a href="keyword-index.html#IO">IO</a> 
This uses the kernel tracepoint block_rq_insert to read the size of I/O. The output includes the name of the process or thread that was on-CPU when the I/O request was inserted on the issue queue.<pre># stap bitesize-nd.stp -T 1</pre>
</li><li><a name="lwtools/execsnoop-nd.stp"></a><a href="#lwtools/execsnoop-nd.stp">&para;</a> <a href="lwtools/execsnoop-nd.stp">lwtools/execsnoop-nd.stp</a> - Trace process exec() with command line argument details (non-debuginfo) 
keywords: <a href="keyword-index.html#IO">IO</a> 
This can identify if CPU is consumed by short-lived processes, by tracing new process execution. It works by tracing exec() from the fork()-&gt;exec() sequence, which means it will not catch new processes that only fork(). It will also show every exec(), including those if a process re-execs.<pre># stap execsnoop-nd.stp -T 1</pre>
</li><li><a name="lwtools/fslatency-nd.stp"></a><a href="#lwtools/fslatency-nd.stp">&para;</a> <a href="lwtools/fslatency-nd.stp">lwtools/fslatency-nd.stp</a> - Measure the distribution of file system synchronous read and write latency (non-debuginfo) 
keywords: <a href="keyword-index.html#IO">IO</a> <a href="keyword-index.html#FILESYSTEM">FILESYSTEM</a> 
This dynamically traces two common file system functions: do_sync_read() and do_sync_write(), and reports a histogram distribution of latency. Many, but not all, file systems and workloads use these functions. Tracing their time provides one view of suffered file system latency.<pre># stap fslatency-nd.stp 1 1</pre>
</li><li><a name="lwtools/fsslower-nd.stp"></a><a href="#lwtools/fsslower-nd.stp">&para;</a> <a href="lwtools/fsslower-nd.stp">lwtools/fsslower-nd.stp</a> - Trace slow file system synchronous reads and writes (non-debuginfo) 
keywords: <a href="keyword-index.html#IO">IO</a> <a href="keyword-index.html#FILESYSTEM">FILESYSTEM</a> 
This dynamically traces two common file system functions: do_sync_read() and do_sync_write(), and shows details of each call that is slower than a threshold. Many, but not all, file systems and workloads use these functions. Tracing their time provides one view of suffered file system latency.<pre># stap fsslower-nd.stp -T 1</pre>
</li><li><a name="lwtools/killsnoop-nd.stp"></a><a href="#lwtools/killsnoop-nd.stp">&para;</a> <a href="lwtools/killsnoop-nd.stp">lwtools/killsnoop-nd.stp</a> - Trace kill() signals showing process and signal details (non-debuginfo) 
keywords: <a href="keyword-index.html#IO">IO</a> 
This traces signals system-wide, including those sent by the kill(1) command, and shows various details.<pre># stap killsnoop-nd.stp -T 1</pre>
</li><li><a name="lwtools/opensnoop-nd.stp"></a><a href="#lwtools/opensnoop-nd.stp">&para;</a> <a href="lwtools/opensnoop-nd.stp">lwtools/opensnoop-nd.stp</a> - Trace open() syscalls showing filenames (non-debuginfo) 
keywords: <a href="keyword-index.html#IO">IO</a> 
This traces the open() syscall system-wide, to show which files are being opened, and by who.<pre># stap opensnoop-nd.stp -T 1</pre>
</li><li><a name="lwtools/rwtime-nd.stp"></a><a href="#lwtools/rwtime-nd.stp">&para;</a> <a href="lwtools/rwtime-nd.stp">lwtools/rwtime-nd.stp</a> - Summarize read() and write() syscall latency (non-debuginfo) 
keywords: <a href="keyword-index.html#IO">IO</a> 
This traces read() and write() syscalls, producing a histogram summary of their durations (aka latencies).<pre># stap rwtime-nd.stp -T 1</pre>
</li><li><a name="lwtools/syscallbypid-nd.stp"></a><a href="#lwtools/syscallbypid-nd.stp">&para;</a> <a href="lwtools/syscallbypid-nd.stp">lwtools/syscallbypid-nd.stp</a> - Count syscalls with process details (non-debuginfo) 
keywords: <a href="keyword-index.html#IO">IO</a> 
This traces syscalls system-wide, and produces a summary report showing their counts by process ID, process name, and syscall types.<pre># stap syscallbypid-nd.stp -T 1</pre>
</li><li><a name="memory/cachestat.stp"></a><a href="#memory/cachestat.stp">&para;</a> <a href="memory/cachestat.stp">memory/cachestat.stp</a> - Count Page Cache Hits and Misses 
keywords: <a href="keyword-index.html#MEMORY">MEMORY</a> <a href="keyword-index.html#BPF">BPF</a> 
Monitors hits and misses to the page cache and reports a count every 5 seconds. Based on a bpftrace tool by David Valin.<pre># stap cachestat.stp -T 1</pre>
</li><li><a name="memory/glibc-malloc.stp"></a><a href="#memory/glibc-malloc.stp">&para;</a> <a href="memory/glibc-malloc.stp">memory/glibc-malloc.stp</a> - Overview glibc malloc internal operations 
keywords: <a href="keyword-index.html#MEMORY">MEMORY</a> <a href="keyword-index.html#PROCESS">PROCESS</a> 
This script reports on internal statistics of the glibc malloc implementation, as used by a process restricted by stap -x/-c<pre># stap glibc-malloc.stp -c &#39;stap --dump-functions&#39;</pre>
</li><li><a name="memory/hugepage_clear_delays.stp"></a><a href="#memory/hugepage_clear_delays.stp">&para;</a> <a href="memory/hugepage_clear_delays.stp">memory/hugepage_clear_delays.stp</a> - Summarize the time each process spends clearing huge pages 
keywords: <a href="keyword-index.html#MEMORY">MEMORY</a> 
When a huge page is initially used by a process it must be cleared of its original contents to avoid leaking information between processes. On x86_64 machines the huge pages are 2MB in size, 512 times larger than a normal 4KB page. Thus, clearing a huge page can delay program execution by a hundred or more microseconds and maybe noticeable to latency sensitive programs. This script will tally the number of times that each process triggers a huge page clear, the total time in microseconds spent clearing the pages, and the average time in microseconds of the huge page clear.<pre># stap hugepage_clear_delays.stp -T 1</pre>
</li><li><a name="memory/hugepage_collapse.stp"></a><a href="#memory/hugepage_collapse.stp">&para;</a> <a href="memory/hugepage_collapse.stp">memory/hugepage_collapse.stp</a> - Log the kernel collapsing normal pages into a huge page 
keywords: <a href="keyword-index.html#MEMORY">MEMORY</a> 
The kernel may attempt to group many normal sized pages into a single huge page to improve TLB performance. This operation may take a significant amount of time and affect program performance. You can identify if huge page collapse operations are occurring with the systemtap hugepage_collapse.stp script.<pre># stap hugepage_collapse.stp -T 1</pre>
</li><li><a name="memory/hugepage_cow_delays.stp"></a><a href="#memory/hugepage_cow_delays.stp">&para;</a> <a href="memory/hugepage_cow_delays.stp">memory/hugepage_cow_delays.stp</a> - Summarize the time each process spends doing copy on write for huge pages 
keywords: <a href="keyword-index.html#MEMORY">MEMORY</a> 
The system may attempt to reduce memory use by having two or more difference processes share the same writeable page in memory. However, when one of the processes write to shared page that is marked copy on write (COW) the page must be duplicated and then modified. On x86_64 machines the huge pages are 2MB in size, 512 times larger than a normal 4KB page. Thus, copy on write operation on a huge page can delay program execution by a hundred or more microseconds and maybe noticeable to latency sensitive programs. This script will tally the number of times that each process triggers a huge page copy on write, the total time in microseconds spent copying the pages, and the average time in microseconds of the huge page copy.<pre># stap hugepage_cow_delays.stp -T 1</pre>
</li><li><a name="memory/hugepage_split.stp"></a><a href="#memory/hugepage_split.stp">&para;</a> <a href="memory/hugepage_split.stp">memory/hugepage_split.stp</a> - Log the kernel splitting huge pages into normal sized pages 
keywords: <a href="keyword-index.html#MEMORY">MEMORY</a> 
Because some portions of the kernel code only work with normal-sized pages the kernel may convert a huge page into a set of normal-sized pages using a split operation. This operation may be relatively expensive and noticeable to latency sensitive programs. You can identify if split operations are occurring with the systemtap hugepage_split.stp script.<pre># stap hugepage_split.stp -T 1</pre>
</li><li><a name="memory/hw_watch_addr.stp"></a><a href="#memory/hw_watch_addr.stp">&para;</a> <a href="memory/hw_watch_addr.stp">memory/hw_watch_addr.stp</a> - Watch a Kernel Address Using Breakpoint Hardware 
keywords: <a href="keyword-index.html#MEMORY">MEMORY</a> <a href="keyword-index.html#WATCHPOINT">WATCHPOINT</a> 
The script will watch accesses to a single kernel address and prints a traceback each time the address is accessed. This script needs to be run as root to allow access to the breakpoint hardware.<pre># stap --all-modules hw_watch_addr.stp 0x`grep &quot;vm_dirty_ratio&quot; \
/proc/kallsyms | awk &#39;{print $1}&#39;` -T 5</pre>
</li><li><a name="memory/hw_watch_sym.stp"></a><a href="#memory/hw_watch_sym.stp">&para;</a> <a href="memory/hw_watch_sym.stp">memory/hw_watch_sym.stp</a> - Watch a Kernel Symbol Using Breakpoint Hardware 
keywords: <a href="keyword-index.html#MEMORY">MEMORY</a> <a href="keyword-index.html#WATCHPOINT">WATCHPOINT</a> 
The script will watch accesses to the starting address of a single kernel symbol and prints a traceback each time the symbol is accessed. This script needs to be run as root to allow access to the breakpoint hardware.<pre># stap --all-modules hw_watch_sym.stp vm_dirty_ratio -T 5</pre>
</li><li><a name="memory/kmalloc-top"></a><a href="#memory/kmalloc-top">&para;</a> <a href="memory/kmalloc-top">memory/kmalloc-top</a> - Show Paths to Kernel Malloc Invocations 
keywords: <a href="keyword-index.html#MEMORY">MEMORY</a> 
The kmalloc-top perl program runs a small systemtap script to collect stack traces for each call to the kmalloc function and counts the time that each stack trace is observed. When kmalloc-top exits it prints out sorted list. The output can be filtered to print only the first N stack traces (-t), stack traces with a minimum counts (-m), or exclude certain stack traces (-e).<a href="memory/kmalloc-top">sample usage in memory/kmalloc-top
</li><li><a name="memory/last_100_frees.stp"></a><a href="#memory/last_100_frees.stp">&para;</a> <a href="memory/last_100_frees.stp">memory/last_100_frees.stp</a> - Log recent free(3) calls. 
keywords: <a href="keyword-index.html#MEMORY">MEMORY</a> <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#BACKTRACE">BACKTRACE</a> 
This script reports on the last few free(3) libc calls done by processes (possibly restricted by stap -x/-c), along with a userspace backtrace at those moments.<a href="memory/last_100_frees.txt">sample usage in memory/last_100_frees.txt
</li><li><a name="memory/mmanonpage.stp"></a><a href="#memory/mmanonpage.stp">&para;</a> <a href="memory/mmanonpage.stp">memory/mmanonpage.stp</a> - Track Virtual Memory System Actions on Anonymous Pages 
keywords: <a href="keyword-index.html#MEMORY">MEMORY</a> 
The mmanonpage.stp script uses the virtual memory tracepoints available in some kernels to track the number of faults, user space frees, page ins, copy on writes and unmaps for anonymous pages. When the script is terminated the counts are printed for each process that allocated pages while the script was running. This script displays the anonymous page statistics for each process that ran while the script is active. It&#39;s useful in debugging leaks in the anonymous regions of a process.<pre># stap mmanonpage.stp -T 1</pre>
</li><li><a name="memory/mmfilepage.stp"></a><a href="#memory/mmfilepage.stp">&para;</a> <a href="memory/mmfilepage.stp">memory/mmfilepage.stp</a> - Track Virtual Memory System Actions on File Backed Pages 
keywords: <a href="keyword-index.html#MEMORY">MEMORY</a> <a href="keyword-index.html#BPF">BPF</a> 
The mmfilepage.stp script uses the virtual memory tracepoints available in some kernels to track the number of faults, copy on writes mapping, and unmapping operations for file backed pages. When the script is terminated the counts are printed for each process that allocated pages while the script was running. The mmfilepage.stp script is useful in debugging leaks in the mapped file regions of a process.<pre># stap mmfilepage.stp -T 1</pre>
</li><li><a name="memory/mmreclaim.stp"></a><a href="#memory/mmreclaim.stp">&para;</a> <a href="memory/mmreclaim.stp">memory/mmreclaim.stp</a> - Track Virtual Memory System Page Reclamation 
keywords: <a href="keyword-index.html#MEMORY">MEMORY</a> 
The mmreclaim.stp script uses the virtual memory tracepoints available in some kernels to track page reclaim activity that occurred while the script was running. It&#39;s useful in debugging performance problems that occur due to page reclamation.<pre># stap mmreclaim.stp -T 1</pre>
</li><li><a name="memory/mmwriteback.stp"></a><a href="#memory/mmwriteback.stp">&para;</a> <a href="memory/mmwriteback.stp">memory/mmwriteback.stp</a> - Track Virtual Memory System Writing to Disk 
keywords: <a href="keyword-index.html#MEMORY">MEMORY</a> <a href="keyword-index.html#BPF">BPF</a> 
The mmwriteback.stp script uses the virtual memory tracepoints available in some kernels to report all of the file writebacks that occur form kupdate, pdflush and kjournald while the script is running. It&#39;s useful in determining where writes are coming from on a supposedly idle system that is experiencing unexpected IO.<pre># stap mmwriteback.stp -T 1</pre>
</li><li><a name="memory/numa_faults.stp"></a><a href="#memory/numa_faults.stp">&para;</a> <a href="memory/numa_faults.stp">memory/numa_faults.stp</a> - Summarize Process Misses across NUMA Nodes 
keywords: <a href="keyword-index.html#MEMORY">MEMORY</a> <a href="keyword-index.html#NUMA">NUMA</a> 
The numa_faults.stp script tracks the read and write pages faults for each process. When the script exits it prints out the total read and write pages faults for each process. The script also provide a break down of page faults per node for each process. This script is useful for determining whether the program has good locality (page faults limited to a single node) on a NUMA computer.<a href="memory/numa_faults.txt">sample usage in memory/numa_faults.txt
</li><li><a name="memory/overcommit.stp"></a><a href="#memory/overcommit.stp">&para;</a> <a href="memory/overcommit.stp">memory/overcommit.stp</a> - Log Failed Process Memory Allocation Due to Overcommit Limits 
keywords: <a href="keyword-index.html#MEMORY">MEMORY</a> <a href="keyword-index.html#LIMITS">LIMITS</a> 
The overcommit.stp script prints a line each time the kernel refuses a memory allocation request from a process because of /proc/sys/vm/overcommit* limits.<pre># stap overcommit.stp -T 1</pre>
</li><li><a name="memory/pfaults.stp"></a><a href="#memory/pfaults.stp">&para;</a> <a href="memory/pfaults.stp">memory/pfaults.stp</a> - Generate Log of Major and Minor Page Faults 
keywords: <a href="keyword-index.html#MEMORY">MEMORY</a> 
The pfaults.stp script generates a simple log for each major and minor page fault that occurs on the system. Each line contains a timestamp (in microseconds) when the page fault servicing was completed, the pid of the process, the address of the page fault, the type of access (read or write), the type of fault (major or minor), and the elapsed time for page fault. This log can be examined to determine where the page faults are occurring.<a href="memory/pfaults.txt">sample usage in memory/pfaults.txt
</li><li><a name="memory/vm.tracepoints.stp"></a><a href="#memory/vm.tracepoints.stp">&para;</a> <a href="memory/vm.tracepoints.stp">memory/vm.tracepoints.stp</a> - Collect Slab Allocation Statistics 
keywords: <a href="keyword-index.html#MEMORY">MEMORY</a> <a href="keyword-index.html#STATISTICS">STATISTICS</a> 
The script will probe all memory slab/slub allocations and collects information about the size of the object (bytes requested) and user-space process in execution. When run over a period of time, it helps to correlate kernel-space memory consumption owing to user-space processes.<a href="memory/vm.tracepoints.txt">sample usage in memory/vm.tracepoints.txt
</li><li><a name="network/autofs4.stp"></a><a href="#network/autofs4.stp">&para;</a> <a href="network/autofs4.stp">network/autofs4.stp</a> - Watch autofs4 Operations 
keywords: <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#NFS">NFS</a> 
Trace key autofs4 operations such as mounting or unmounting remote filesystems.<pre># stap autofs4.stp -T 1</pre>
</li><li><a name="network/connect_stat.stp"></a><a href="#network/connect_stat.stp">&para;</a> <a href="network/connect_stat.stp">network/connect_stat.stp</a> - Show Process Ancestry for IP Connections 
keywords: <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#SOCKET">SOCKET</a> <a href="keyword-index.html#PROCESS">PROCESS</a> 
The connect_stat.stp script prints a task&#39;s entire ancestry (parent process name/uid/gid) whenever it attempts an outgoing socket connection to a given IP address.<pre># stap connect_stat.stp 127.0.0.1 -T 1</pre>
</li><li><a name="network/dropwatch.stp"></a><a href="#network/dropwatch.stp">&para;</a> <a href="network/dropwatch.stp">network/dropwatch.stp</a> - Watch Where Socket Buffers Are Freed in the Kernel 
keywords: <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#TRACEPOINT">TRACEPOINT</a> <a href="keyword-index.html#SOCKET">SOCKET</a> 
Every five seconds the dropwatch.stp script lists the number of socket buffers freed at locations in the kernel.<pre># stap dropwatch.stp -T 1</pre>
</li><li><a name="network/net_xmit_json.stp"></a><a href="#network/net_xmit_json.stp">&para;</a> <a href="network/net_xmit_json.stp">network/net_xmit_json.stp</a> - Tracks time between packet queue and transmit. 
keywords: <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#STATISTICS">STATISTICS</a> <a href="keyword-index.html#JSON">JSON</a> 
This script tracks time between packet queue and transmit. The information is provided to userspace via procfs in JSON format.<pre># stap net_xmit_json.stp -T 1</pre>
</li><li><a name="network/netdev.stp"></a><a href="#network/netdev.stp">&para;</a> <a href="network/netdev.stp">network/netdev.stp</a> - Trace Activity on Network Devices 
keywords: <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#TRAFFIC">TRAFFIC</a> 
The netdev.stp script traces configuration and transmit/receive activity on network devices.<pre># stap netdev.stp -T 1</pre>
</li><li><a name="network/netfilter_drop.stp"></a><a href="#network/netfilter_drop.stp">&para;</a> <a href="network/netfilter_drop.stp">network/netfilter_drop.stp</a> - System-Wide Network Packet Dropping Tool 
keywords: <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#PACKETS">PACKETS</a> <a href="keyword-index.html#GURU">GURU</a> 
The script drops the specified number of packets of the specified protocol. Valid protocols are TCP, UDP, or ALL. If ALL is specified, all incoming packets are dropped. The number of packets to drop can be specified with a positive integer. A value of 0 indicates that packets should be dropped until the user manually exits.<pre># stap -g netfilter_drop.stp TCP 1 -T 2</pre>
</li><li><a name="network/netfilter_summary.stp"></a><a href="#network/netfilter_summary.stp">&para;</a> <a href="network/netfilter_summary.stp">network/netfilter_summary.stp</a> - System-Wide Count of Network Packets by IPs 
keywords: <a href="keyword-index.html#_BEST">_BEST</a> <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#TRAFFIC">TRAFFIC</a> 
The script watches all IPv4 network traffic on the system. On exit the script prints a list showing the number of packets sent along source IP address / destination IP address pair encountered, and the total number of bytes sent among the pair. The list is ordered from greatest to least number of packets seen among the source/destination pairs.<a href="network/netfilter_summary.txt">sample usage in network/netfilter_summary.txt
</li><li><a name="network/netfilter_summary_json.stp"></a><a href="#network/netfilter_summary_json.stp">&para;</a> <a href="network/netfilter_summary_json.stp">network/netfilter_summary_json.stp</a> - System-Wide Count of Network Packets by IPs 
keywords: <a href="keyword-index.html#_BEST">_BEST</a> <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#TRAFFIC">TRAFFIC</a> <a href="keyword-index.html#JSON">JSON</a> 
The script watches all IPv4 network traffic on the system. The data is output in JSON format and includes the number of packets sent along source IP address / destination IP address pair encountered, and the total number of bytes sent among the pair.<pre># stap netfilter_summary_json.stp -T 1</pre>
</li><li><a name="network/nettop.stp"></a><a href="#network/nettop.stp">&para;</a> <a href="network/nettop.stp">network/nettop.stp</a> - Periodic Listing of Processes Using Network Interfaces 
keywords: <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#TRAFFIC">TRAFFIC</a> 
Every five seconds the nettop.stp script prints out a list of processed (PID and command) with the number of packets sent/received and the amount of data sent/received by the process during that interval.<a href="network/nettop.txt">sample usage in network/nettop.txt
</li><li><a name="network/nfsd-recent.stp"></a><a href="#network/nfsd-recent.stp">&para;</a> <a href="network/nfsd-recent.stp">network/nfsd-recent.stp</a> - Keep track of NFS server statistics 
keywords: <a href="keyword-index.html#NFS">NFS</a> <a href="keyword-index.html#STATISTICS">STATISTICS</a> 
This script tracks all nfsd server operations by client_ip address, and periodically lists those clients that have made recent requests. It&#39;s a way of finding out which nfs clients might be considered still connected.<pre># stap nfsd-recent.stp -T 1</pre>
</li><li><a name="network/nfsd-trace.stp"></a><a href="#network/nfsd-trace.stp">&para;</a> <a href="network/nfsd-trace.stp">network/nfsd-trace.stp</a> - Trace NFSD requests with file names. 
keywords: <a href="keyword-index.html#NFS">NFS</a> <a href="keyword-index.html#TRACE">TRACE</a> 
This script traces all nfsd server operations by client_ip address, operation, and complete file name (if possible).<a href="network/nfsd-trace.txt">sample usage in network/nfsd-trace.txt
</li><li><a name="network/nfsd_unlink.stp"></a><a href="#network/nfsd_unlink.stp">&para;</a> <a href="network/nfsd_unlink.stp">network/nfsd_unlink.stp</a> - Find Which Client Is Removing NFS Files on Server 
keywords: <a href="keyword-index.html#NFS">NFS</a> <a href="keyword-index.html#DISK">DISK</a> 
The nfsd_unlink.stp script lists the ip address and file name each time time a file is being removed or unlinked by the nfsd. This script is run on the nfs server.<pre># stap nfsd_unlink.stp -T 1</pre>
</li><li><a name="network/nfsdtop.stp"></a><a href="#network/nfsdtop.stp">&para;</a> <a href="network/nfsdtop.stp">network/nfsdtop.stp</a> - Keep track of NFS server statistics 
keywords: <a href="keyword-index.html#NFS">NFS</a> <a href="keyword-index.html#STATISTICS">STATISTICS</a> 
The nfsdtop.stp script gathers and displays NFS lookups,<pre># stap nfsdtop.stp -T 1</pre>
</li><li><a name="network/packet_contents.stp"></a><a href="#network/packet_contents.stp">&para;</a> <a href="network/packet_contents.stp">network/packet_contents.stp</a> - Network packet contents 
keywords: <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#TRAFFIC">TRAFFIC</a> 
The packet_contents.stp script displays the length of each network packet and its contents in both hexadecimal and ASCII. Systemtap strings are MAXSTRINGLEN in length by default which may not be enough for larger packets. In order to print larger packets, this limit can be increased by passing in the &quot;-DMAXSTRINGLEN=65536&quot; command line option.<a href="network/packet_contents.txt">sample usage in network/packet_contents.txt
</li><li><a name="network/sk_stream_wait_memory.stp"></a><a href="#network/sk_stream_wait_memory.stp">&para;</a> <a href="network/sk_stream_wait_memory.stp">network/sk_stream_wait_memory.stp</a> - Track Start and Stop of Processes Due to Network Buffer Space 
keywords: <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#TCP">TCP</a> <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#BPF">BPF</a> 
The sk_stream-wait_memory.stp prints a time stamp, executable, and pid each time a process blocks due to the send buffer being full. A similar entry is printed each time a process continues because there is room in the buffer.<pre># stap sk_stream_wait_memory.stp -T 1</pre>
</li><li><a name="network/socket-trace.stp"></a><a href="#network/socket-trace.stp">&para;</a> <a href="network/socket-trace.stp">network/socket-trace.stp</a> - Trace Functions Called in Network Socket Code 
keywords: <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#SOCKET">SOCKET</a> 
The script instruments each of the functions in the Linux kernel&#39;s net/socket.c file. The script prints out trace data. The first element of a line is time delta in microseconds from the previous entry. This is followed by the command name and the PID. The &quot;-&gt;&quot; and &quot;&lt;-&quot; indicates function entry and function exit, respectively. The last element of the line is the function name.<pre># stap socket-trace.stp -T 1</pre>
</li><li><a name="network/socktop"></a><a href="#network/socktop">&para;</a> <a href="network/socktop">network/socktop</a> - Periodically Summarize Socket Activity on the System 
keywords: <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#SOCKET">SOCKET</a> 
The socktop script periodically prints out a list of the processes with the highest socket activity. Command line options for the script allow filtering to focus on particular types of sockets. The &quot;-h&quot; option lists socktop script&#39;s filtering options.<a href="network/socktop">sample usage in network/socktop
</li><li><a name="network/stp_dump.stp"></a><a href="#network/stp_dump.stp">&para;</a> <a href="network/stp_dump.stp">network/stp_dump.stp</a> - Dump of STP packets 
keywords: <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#TRAFFIC">TRAFFIC</a> 
The stp_dump.stp prints out the packet contents. Each block contains the STP protocol ID, version ID, flags, root and bridge MAC addresses, and various times.<a href="network/stp_dump.txt">sample usage in network/stp_dump.txt
</li><li><a name="network/tcp_connections.stp"></a><a href="#network/tcp_connections.stp">&para;</a> <a href="network/tcp_connections.stp">network/tcp_connections.stp</a> - Track Creation of Incoming TCP Connections 
keywords: <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#TCP">TCP</a> <a href="keyword-index.html#SOCKET">SOCKET</a> 
The tcp_connections.stp script prints information for each new incoming TCP connection accepted by the computer. The information includes the UID, the command accepting the connection, the PID of the command, the port the connection is on, and the IP address of the originator of the request.<pre># stap tcp_connections.stp -T 1</pre>
</li><li><a name="network/tcp_init_cwnd.stp"></a><a href="#network/tcp_init_cwnd.stp">&para;</a> <a href="network/tcp_init_cwnd.stp">network/tcp_init_cwnd.stp</a> - Increase Initial TCP Congestion Window to 10 
keywords: <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#TCP">TCP</a> <a href="keyword-index.html#SOCKET">SOCKET</a> <a href="keyword-index.html#GURU">GURU</a> 
Run the tcp_init_cwnd.stp script in the background to override a kernel&#39;s default tcp cwnd value to 10, which has been found to improve latency for web server type workloads. The script prints a count of cwnd value changes when it is stopped.<pre># stap -g tcp_init_cwnd.stp -T 1</pre>
</li><li><a name="network/tcp_retransmission.stp"></a><a href="#network/tcp_retransmission.stp">&para;</a> <a href="network/tcp_retransmission.stp">network/tcp_retransmission.stp</a> - print tcp retransmission packet 
keywords: <a href="keyword-index.html#TCP">TCP</a> <a href="keyword-index.html#RETRANSMISSION">RETRANSMISSION</a> 
The tcp_retransmission.stp prints out a line for each tcp retransmission packet<pre># stap tcp_retransmission.stp -T 1</pre>
</li><li><a name="network/tcp_trace.stp"></a><a href="#network/tcp_trace.stp">&para;</a> <a href="network/tcp_trace.stp">network/tcp_trace.stp</a> - TCP Connection Tracing Utility 
keywords: <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#TRACE">TRACE</a> 
This scripts traces a given TCP connection based on the filter parameters given by the user. The indexing is done by the 4 tuples local address, remote address, local port, remote port.<a href="network/tcp_trace.txt">sample usage in network/tcp_trace.txt
</li><li><a name="network/tcpdumplike.stp"></a><a href="#network/tcpdumplike.stp">&para;</a> <a href="network/tcpdumplike.stp">network/tcpdumplike.stp</a> - Dump of Received UDP/TCP Packets 
keywords: <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#TRAFFIC">TRAFFIC</a> 
The tcpdumplike.stp prints out a line for each TCP &amp; UDP packet received. Each line includes the source and destination IP addresses, the source and destination ports, and flags.<pre># stap tcpdumplike.stp -T 1</pre>
</li><li><a name="network/tcpipstat.stp"></a><a href="#network/tcpipstat.stp">&para;</a> <a href="network/tcpipstat.stp">network/tcpipstat.stp</a> - Display Network Statistics for Individual TCP Sockets 
keywords: <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#STATISTICS">STATISTICS</a> 
The tcpipstat script collects and displays network statistics related to individual TCP sockets or groups of sockets. The statistics that are collected are simular to that of the command netstat -s, only sorted and grouped by individual sockets.<a href="network/tcpipstat.txt">sample usage in network/tcpipstat.txt
</li><li><a name="network/who_sent_it.stp"></a><a href="#network/who_sent_it.stp">&para;</a> <a href="network/who_sent_it.stp">network/who_sent_it.stp</a> - Trace threads sending network traffic to given host and/or port 
keywords: <a href="keyword-index.html#NETWORK">NETWORK</a> <a href="keyword-index.html#TRACE">TRACE</a> <a href="keyword-index.html#TRAFFIC">TRAFFIC</a> <a href="keyword-index.html#SIMPLE">SIMPLE</a> 
This script traces outgoing network packets using the netfilter probes (not requiring debuginfo), printing the source thread name/id and destination host:port. It may be filtered with the_dport and the_daddr globals, e.g., to watch only for DNS traffic (port 53), and/or only to the localhost (127.0.0.1).<a href="network/who_sent_it.txt">sample usage in network/who_sent_it.txt
</li><li><a name="process/auditbt.stp"></a><a href="#process/auditbt.stp">&para;</a> <a href="process/auditbt.stp">process/auditbt.stp</a> - Generate backtraces for kernel audit events 
keywords: <a href="keyword-index.html#MONITORING">MONITORING</a> <a href="keyword-index.html#SECURITY">SECURITY</a> <a href="keyword-index.html#BACKTRACE">BACKTRACE</a> 
Attaches to the kernel audit-log paths (also used by libaudit), and log every record being sent, along with a user-space backtrace of the process that caused it.<pre># stap auditbt.stp -d /usr/bin/sudo --ldd -c &quot;sudo true&quot;</pre>
</li><li><a name="process/chng_cpu.stp"></a><a href="#process/chng_cpu.stp">&para;</a> <a href="process/chng_cpu.stp">process/chng_cpu.stp</a> - Monitor Changes in Processor Executing a Task 
keywords: <a href="keyword-index.html#SCHEDULER">SCHEDULER</a> 
The chng_cpu.stp script takes an argument which is the executable name of the task it should monitor. Each time a task with that executable name is found running on a different processor, the script prints out the thread id (tid), the executable name, the processor now running the task, the thread state, and a backtrace showing the kernel functions that triggered the running of the task on the processor.<pre># stap chng_cpu.stp -T 1 bash</pre>
</li><li><a name="process/cycle_thief.stp"></a><a href="#process/cycle_thief.stp">&para;</a> <a href="process/cycle_thief.stp">process/cycle_thief.stp</a> - Track IRQ's and Other Processes Stealing Cycles from a Task 
keywords: <a href="keyword-index.html#_BEST">_BEST</a> <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#SCHEDULER">SCHEDULER</a> <a href="keyword-index.html#TIME">TIME</a> <a href="keyword-index.html#TRACEPOINT">TRACEPOINT</a> <a href="keyword-index.html#INTERRUPT">INTERRUPT</a> 
The cycle_thief.stp script instruments the scheduler and IRQ handler to determine which processes and interrupts are competing with the specified task for the cpu cycles. This script uses the &#39;-c&#39; or &#39;-x&#39; options to focus on a specific task. The script output the number of times the task migrates between processors, histograms showing the length of time on and off processor, lists of processes running while the task is off the processor, and the interrupts that occurred while the task was running.<a href="process/cycle_thief.txt">sample usage in process/cycle_thief.txt
</li><li><a name="process/errsnoop.stp"></a><a href="#process/errsnoop.stp">&para;</a> <a href="process/errsnoop.stp">process/errsnoop.stp</a> - Tabulate System Call Errors 
keywords: <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#SYSCALL">SYSCALL</a> 
Prints a periodic tabular report about failing system calls, by process and by syscall failure. The first optional argument specifies the reporting interval (in seconds, default 5); the second optional argument gives a screen height (number of lines in the report, default 20).<pre># stap errsnoop.stp 1 10 -T 1</pre>
</li><li><a name="process/forktracker.stp"></a><a href="#process/forktracker.stp">&para;</a> <a href="process/forktracker.stp">process/forktracker.stp</a> - Trace Creation of Processes 
keywords: <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#SCHEDULER">SCHEDULER</a> 
The forktracker.stp script prints out a time-stamped entry showing each fork and exec operation on the machine. This can be useful to determine what process is creating a flurry of short-lived processes.<pre># stap forktracker.stp -T 1</pre>
</li><li><a name="process/futexes.stp"></a><a href="#process/futexes.stp">&para;</a> <a href="process/futexes.stp">process/futexes.stp</a> - System-Wide Futex Contention 
keywords: <a href="keyword-index.html#SYSCALL">SYSCALL</a> <a href="keyword-index.html#LOCKING">LOCKING</a> <a href="keyword-index.html#FUTEX">FUTEX</a> 
The script watches the futex syscall on the system. On exit the futex&#39;s address, the number of contentions, and the average time for each contention on the futex are printed from lowest pid number to highest.<a href="process/futexes.txt">sample usage in process/futexes.txt
</li><li><a name="process/futexes2.stp"></a><a href="#process/futexes2.stp">&para;</a> <a href="process/futexes2.stp">process/futexes2.stp</a> - System-Wide Shared Futex Contention 
keywords: <a href="keyword-index.html#SYSCALL">SYSCALL</a> <a href="keyword-index.html#LOCKING">LOCKING</a> <a href="keyword-index.html#FUTEX">FUTEX</a> 
The script watches just shared futex syscalls on the system. On exit the futex&#39;s key, the number of contentions, and the average time for each contention on the futex are printed from lowest pid number to highest.<pre># stap futexes2.stp -T 1</pre>
</li><li><a name="process/ltrace.stp"></a><a href="#process/ltrace.stp">&para;</a> <a href="process/ltrace.stp">process/ltrace.stp</a> - uprobes-based ltrace 
keywords: <a href="keyword-index.html#PROCESS">PROCESS</a> 
The ltrace.stp script lists calls that the designated process makes through PLTs (procedure linkage tables), generally into shared libraries.<pre># stap ltrace.stp -c ls || echo PR14738</pre>
</li><li><a name="process/migrate.stp"></a><a href="#process/migrate.stp">&para;</a> <a href="process/migrate.stp">process/migrate.stp</a> - Track the Migration of Specific Executables 
keywords: <a href="keyword-index.html#SCHEDULER">SCHEDULER</a> 
The migrate.stp script takes an argument which is the executable name of the task it should monitor. Each time a task with that executable name migrates between processors an entry is printed with the process id (pid), the executable name, the processor off loading the task, and the process taking the task. Note that the task may or may not be executing at the time of the migration.<pre># stap migrate.stp -T 1 bash</pre>
</li><li><a name="process/mutex-contention.stp"></a><a href="#process/mutex-contention.stp">&para;</a> <a href="process/mutex-contention.stp">process/mutex-contention.stp</a> - pthread mutex contention analysis 
keywords: <a href="keyword-index.html#LOCKING">LOCKING</a> 
Tracks pthread-mutex initialization/use and underlying futex operations, to identify (with backtraces/symbol-names) the mutexes suffering most contention. Invoke with &quot;-d SHLIB --ldd&quot;, perhaps with -DMAXMAPENTRIES=NNNN for some large NNNN, if the arrays overflow due to heavy activity.<pre># stap mutex-contention.stp -T 1</pre>
</li><li><a name="process/noptrace.stp"></a><a href="#process/noptrace.stp">&para;</a> <a href="process/noptrace.stp">process/noptrace.stp</a> - Disable ptrace from Hierarchies of Processes 
keywords: <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#SECURITY">SECURITY</a> <a href="keyword-index.html#GURU">GURU</a> 
Blocks ptrace(2) attempts from processes identified by stap -c/-x, as also specifiable from /proc/systemtap/stap_XXX/ control files. Processes may be added or removed from the blocked list.<a href="process/noptrace.txt">sample usage in process/noptrace.txt
</li><li><a name="process/pfiles.stp"></a><a href="#process/pfiles.stp">&para;</a> <a href="process/pfiles.stp">process/pfiles.stp</a> - Print Process File Descriptors 
keywords: <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#FILE">FILE</a> 
Run pfiles.stp to produce a human-readable summary of all open file descriptors of a given process. Specify the process-id as -x PID for fastest performance.<pre># stap -g pfiles.stp -x $$</pre>
</li><li><a name="process/plimit.stp"></a><a href="#process/plimit.stp">&para;</a> <a href="process/plimit.stp">process/plimit.stp</a> - Print Resource Limits of Process 
keywords: <a href="keyword-index.html#PROCESS">PROCESS</a> 
The script prints a variety of resource limits for a given pid, like /proc/$$/limits on recent kernels.<pre># stap -g plimit.stp $$</pre>
</li><li><a name="process/procmod_watcher.stp"></a><a href="#process/procmod_watcher.stp">&para;</a> <a href="process/procmod_watcher.stp">process/procmod_watcher.stp</a> - Monitor process creation/termination and module [un]loading 
keywords: <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#MONITORING">MONITORING</a> <a href="keyword-index.html#SYSCALL">SYSCALL</a> <a href="keyword-index.html#TRACEPOINT">TRACEPOINT</a> 
The procmod_watcher.stp script monitors calls to fork(), exec(), exit(), init_module(), and delete_module(). Event-specific details are also printed out (e.g. for exec(), the file being exec&#39;ed). This script does not require debuginfo.<pre># stap procmod_watcher.stp -T 1</pre>
</li><li><a name="process/proctop.stp"></a><a href="#process/proctop.stp">&para;</a> <a href="process/proctop.stp">process/proctop.stp</a> - Periodically Print Process Information With History 
keywords: <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#SCHEDULER">SCHEDULER</a> <a href="keyword-index.html#_BEST">_BEST</a> 
Every 5 seconds, print out a list of 25 processes that took the most system time with information about the processes. Includes information on processes that may have exited while the script was running. The script contains configuration options listed in the script source.<a href="process/proctop.txt">sample usage in process/proctop.txt
</li><li><a name="process/psig.stp"></a><a href="#process/psig.stp">&para;</a> <a href="process/psig.stp">process/psig.stp</a> - Print Process File Descriptors 
keywords: <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#SIGNALS">SIGNALS</a> 
Run psig.stp to produce a human-readable summary of the signal handling configuration of a given process. Specify the process-id as -x PID for fastest performance.<pre># stap -DMAXACTION=10000 -g psig.stp -x $$</pre>
</li><li><a name="process/pstrace_exec.stp"></a><a href="#process/pstrace_exec.stp">&para;</a> <a href="process/pstrace_exec.stp">process/pstrace_exec.stp</a> - Print trace of process ancestors for matching exec commands 
keywords: <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#BACKTRACE">BACKTRACE</a> 
The pstrace_exec.stp script watches each exec operation. If the exec contains a substring that matches the script&#39;s command-line argument, it prints out that process and all of its ancestors.<pre># stap pstrace_exec.stp -T 1 bash</pre>
</li><li><a name="process/pstree.stp"></a><a href="#process/pstree.stp">&para;</a> <a href="process/pstree.stp">process/pstree.stp</a> - Generates a process diagram in DOT form. 
keywords: <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#DIAGRAM">DIAGRAM</a> 
The pstree.stp script generates a process diagram in DOT form. For instance, it may be useful on a &#39;make&#39; command to see all the processes that are started.<pre># stap pstree.stp -T 1</pre>
</li><li><a name="process/rlimit_nofile.stp"></a><a href="#process/rlimit_nofile.stp">&para;</a> <a href="process/rlimit_nofile.stp">process/rlimit_nofile.stp</a> - Trace processes running out of file descriptors 
keywords: <a href="keyword-index.html#LIMITS">LIMITS</a> 
This script watches processes being scheduled and which try to allocate a file descriptor without luck.<pre># stap rlimit_nofile.stp -T 1</pre>
</li><li><a name="process/sched-latency.stp"></a><a href="#process/sched-latency.stp">&para;</a> <a href="process/sched-latency.stp">process/sched-latency.stp</a> - track wakeup-to-dispatch latency stats 
keywords: <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#SCHEDULER">SCHEDULER</a> <a href="keyword-index.html#TIME">TIME</a> <a href="keyword-index.html#TRACEPOINT">TRACEPOINT</a> 
This script periodically reports a histogram of the latency between a task (thread) being woken up and it actually being dispatched to a CPU: the amount of time it&#39;s spent in the runnable queue.<a href="process/sched-latency.txt">sample usage in process/sched-latency.txt
</li><li><a name="process/schedtimes.stp"></a><a href="#process/schedtimes.stp">&para;</a> <a href="process/schedtimes.stp">process/schedtimes.stp</a> - Track Time Processes Spend in Various States Using Tracepoints 
keywords: <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#SCHEDULER">SCHEDULER</a> <a href="keyword-index.html#TIME">TIME</a> <a href="keyword-index.html#TRACEPOINT">TRACEPOINT</a> 
The schedtimes.stp script instruments the scheduler to track the amount of time that each process spends in running, sleeping, queuing, and waiting for io. On exit the script prints out the accumulated time for each state of processes observed. Optionally, this script can be used with the &#39;-c&#39; or &#39;-x&#39; options to focus on a specific PID and its children.<a href="process/schedtimes.txt">sample usage in process/schedtimes.txt
</li><li><a name="process/semop-watch.stp"></a><a href="#process/semop-watch.stp">&para;</a> <a href="process/semop-watch.stp">process/semop-watch.stp</a> - Watch semop(2)/semtimedop(2) operations 
keywords: <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#LOCKING">LOCKING</a> 
Prints a timed trace of semop(2)/semtimedop(2) syscalls<pre># stap semop-watch.stp -c &#39;sleep 2&#39;</pre>
</li><li><a name="process/sig_by_pid.stp"></a><a href="#process/sig_by_pid.stp">&para;</a> <a href="process/sig_by_pid.stp">process/sig_by_pid.stp</a> - Signal Counts by Process ID 
keywords: <a href="keyword-index.html#SIGNALS">SIGNALS</a> 
Print signal counts by process ID in descending order.<a href="process/sig_by_pid.txt">sample usage in process/sig_by_pid.txt
</li><li><a name="process/sig_by_proc.stp"></a><a href="#process/sig_by_proc.stp">&para;</a> <a href="process/sig_by_proc.stp">process/sig_by_proc.stp</a> - Signal Counts by Process Name 
keywords: <a href="keyword-index.html#SIGNALS">SIGNALS</a> 
Print signal counts by process name in descending order.<a href="process/sig_by_proc.txt">sample usage in process/sig_by_proc.txt
</li><li><a name="process/sigkill.stp"></a><a href="#process/sigkill.stp">&para;</a> <a href="process/sigkill.stp">process/sigkill.stp</a> - Track SIGKILL Signals 
keywords: <a href="keyword-index.html#SIGNALS">SIGNALS</a> 
The script traces any SIGKILL signals. When that SIGKILL signal is sent to a process, the script prints out the signal name, the destination executable and process ID, the executable name and user ID that sents the signal.<pre># stap sigkill.stp -T 1</pre>
</li><li><a name="process/sigmon.stp"></a><a href="#process/sigmon.stp">&para;</a> <a href="process/sigmon.stp">process/sigmon.stp</a> - Track a Particular Signal to a Specific Process 
keywords: <a href="keyword-index.html#SIGNALS">SIGNALS</a> 
The script watches for a particular signal sent to a specific process. When that signal is sent to the specified process, the script prints out the PID and executable of the process sending the signal, the PID and executable name of the process receiving the signal, and the signal number and name.<pre># stap sigmon.stp -T 1 SIGKILL</pre>
</li><li><a name="process/sleepingBeauties.stp"></a><a href="#process/sleepingBeauties.stp">&para;</a> <a href="process/sleepingBeauties.stp">process/sleepingBeauties.stp</a> - Generate Backtraces of Threads Waiting for IO Operations 
keywords: <a href="keyword-index.html#IO">IO</a> <a href="keyword-index.html#SCHEDULER">SCHEDULER</a> <a href="keyword-index.html#BACKTRACE">BACKTRACE</a> 
The script monitors the time that threads spend in waiting for IO operations (in &quot;D&quot; state) in the wait_for_completion function. If a thread spends over 10ms, its name and backtrace is printed, and later so is the total delay.<pre># stap sleepingBeauties.stp -T 1</pre>
</li><li><a name="process/sleeptime.stp"></a><a href="#process/sleeptime.stp">&para;</a> <a href="process/sleeptime.stp">process/sleeptime.stp</a> - Trace Time Spent in Nanosleep Syscalls 
keywords: <a href="keyword-index.html#SYSCALL">SYSCALL</a> <a href="keyword-index.html#NANOSLEEP">NANOSLEEP</a> 
The script watches each nanosleep syscall on the system. At the end of each nanosleep syscall the script prints out a line with a timestamp in microseconds, the pid, the executable name in parentheses, the &quot;nanosleep:&quot; key, and the duration of the sleep in microseconds.<pre># stap sleeptime.stp -T 1</pre>
</li><li><a name="process/spawn_seeker.stp"></a><a href="#process/spawn_seeker.stp">&para;</a> <a href="process/spawn_seeker.stp">process/spawn_seeker.stp</a> - Track Creation of Processes by process and execname 
keywords: <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#SCHEDULER">SCHEDULER</a> 
The spawn_seeker.stp script every minute (and on exit) prints out the local time and sorted lists of which processes and executables spawned tasks during the previous minute. This can be useful to determine what process is creating a flurry of short-lived processes. When a process exits its count of tasks created is added to its parent&#39;s count to better account for the indirect task creation by children processes. For more detailed examination of task creation consider using forktracker.stp.<a href="process/spawn_seeker.txt">sample usage in process/spawn_seeker.txt
</li><li><a name="process/strace.stp"></a><a href="#process/strace.stp">&para;</a> <a href="process/strace.stp">process/strace.stp</a> - Trace system calls 
keywords: <a href="keyword-index.html#_BEST">_BEST</a> <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#SYSCALL">SYSCALL</a> 
The script loosely emulates strace, when applied to individual processes or hierarchies (via -c/-x), or the entire system (without -c/-x). A few output configuration parameters may be set with -G.<a href="process/strace.txt">sample usage in process/strace.txt
</li><li><a name="process/syscalls_by_pid.stp"></a><a href="#process/syscalls_by_pid.stp">&para;</a> <a href="process/syscalls_by_pid.stp">process/syscalls_by_pid.stp</a> - System-Wide Count of Syscalls by PID 
keywords: <a href="keyword-index.html#SYSCALL">SYSCALL</a> 
The script watches all syscall on the system. On exit the script prints a list showing the number of systemcalls executed by each PID ordered from greatest to least number of syscalls.<a href="process/syscalls_by_pid.txt">sample usage in process/syscalls_by_pid.txt
</li><li><a name="process/syscalls_by_proc.stp"></a><a href="#process/syscalls_by_proc.stp">&para;</a> <a href="process/syscalls_by_proc.stp">process/syscalls_by_proc.stp</a> - System-Wide Count of Syscalls by Executable 
keywords: <a href="keyword-index.html#SYSCALL">SYSCALL</a> 
The script watches all syscall on the system. On exit the script prints a list showing the number of systemcalls executed by each executable ordered from greatest to least number of syscalls.<a href="process/syscalls_by_proc.txt">sample usage in process/syscalls_by_proc.txt
</li><li><a name="process/syscalltimes"></a><a href="#process/syscalltimes">&para;</a> <a href="process/syscalltimes">process/syscalltimes</a> - System-Wide Syscall Statistics with Filtering 
keywords: <a href="keyword-index.html#SYSCALL">SYSCALL</a> 
Combination shell/systemtap script to measure system call counts and times. Can be filtered by process IDs, process names and users.<a href="process/syscalltimes">sample usage in process/syscalltimes
</li><li><a name="process/thread-business.stp"></a><a href="#process/thread-business.stp">&para;</a> <a href="process/thread-business.stp">process/thread-business.stp</a> - monitor syscall history 
keywords: <a href="keyword-index.html#_BEST">_BEST</a> <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#SYSCALL">SYSCALL</a> 
Prints a periodic tabular report about the counts of syscall activity of all threads on the system, along with a textual recent-syscall-history for each<a href="process/thread-business.txt">sample usage in process/thread-business.txt
</li><li><a name="process/threadstacks.stp"></a><a href="#process/threadstacks.stp">&para;</a> <a href="process/threadstacks.stp">process/threadstacks.stp</a> - Override default new-pthread stack sizes 
keywords: <a href="keyword-index.html#THREAD">THREAD</a> <a href="keyword-index.html#GURU">GURU</a> 
Overrides default NPTL pthread_create stack size for all new threads created by target processes. Reports one line per process when the related glibc variable __default_stacksize is updated. Moot for glibc versions that support $LIBC_PTHREAD_DEFAULT_STACKSIZE_NP.<pre># stap -g threadstacks.stp -Gsize=65536 -T 1 -d `which stap`</pre>
</li><li><a name="process/wait4time.stp"></a><a href="#process/wait4time.stp">&para;</a> <a href="process/wait4time.stp">process/wait4time.stp</a> - Trace Time Spent in wait4 Syscalls 
keywords: <a href="keyword-index.html#SYSCALL">SYSCALL</a> <a href="keyword-index.html#PROCESS">PROCESS</a> 
The script watches each wait4 syscall on the system. At the end of each wait4 syscall the script prints out a line with a timestamp in microseconds, the pid, the executable name in parentheses, the &quot;wait4:&quot; key, the duration of the wait and the PID that the wait4 was waiting for. If the waited for PID is not specified , it is &quot;-1&quot;.<pre># stap wait4time.stp -T 1</pre>
</li><li><a name="profiling/container_check.stp"></a><a href="#profiling/container_check.stp">&para;</a> <a href="profiling/container_check.stp">profiling/container_check.stp</a> - Monitor capabilities and syscalls used by a process and it children 
keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> <a href="keyword-index.html#CONTAINER">CONTAINER</a> <a href="keyword-index.html#SYSCALL">SYSCALL</a> 
The container_check.stp script monitors the use of linux capablities and optionally forbidden syscalls by a process and its children. On exit the script prints out lists showing the capabilies used by each executable, which syscall used specific capabilites for each executable, a list of forbidden syscalls used, and details on any syscalls that failed during monitoring. This script is designed to help diagnose issues caused by restricted capabilies and syscalls when running an application in a container. If the script warns about skipped probes, the number of active kretprobes may need to be increased with &quot;-DKRETACTIVE=100&quot; option on the command line<pre># stap container_check.stp -c &quot;ping -c 1 sourceware.org || true&quot;</pre>
</li><li><a name="profiling/errno.stp"></a><a href="#profiling/errno.stp">&para;</a> <a href="profiling/errno.stp">profiling/errno.stp</a> - Show Which Processes and System Calls Return Errors Most Frequently 
keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> 
On exit the errno.stp script provides a sorted list showing which combination of PID, system call, and error occur most frequently.<pre># stap errno.stp -T 1</pre>
</li><li><a name="profiling/fileline-profile.stp"></a><a href="#profiling/fileline-profile.stp">&para;</a> <a href="profiling/fileline-profile.stp">profiling/fileline-profile.stp</a> - Profile Kernel/User Functions 
keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> 
The fileline-profile.stp script ends by printing out a sorted list of the top twenty kernel and/or user processes providing file:line information, if available, from the samples addresses gathered over the time period the script is run. Use any of --ldd, --all-modules, -d MODULE, -d /PATH/TO/EXEC to add more symbolic info. To include the symbol name in the output, specify guru mode (-g) and add symbolname=&quot;yes&quot; to the stap command.<pre># stap fileline-profile.stp -T 6 --all-modules --ldd</pre>
</li><li><a name="profiling/fntimes.stp"></a><a href="#profiling/fntimes.stp">&para;</a> <a href="profiling/fntimes.stp">profiling/fntimes.stp</a> - Show Functions Taking Longer Than Usual 
keywords: <a href="keyword-index.html#_BEST">_BEST</a> <a href="keyword-index.html#PROFILING">PROFILING</a> 
The fntimes.stp script monitors the execution time history of a given function family (assumed non-recursive). Each time (beyond a warmup interval) is then compared to the historical maximum. If it exceeds a certain threshold (250%), a message is printed.<a href="profiling/fntimes.txt">sample usage in profiling/fntimes.txt
</li><li><a name="profiling/functioncallcount.stp"></a><a href="#profiling/functioncallcount.stp">&para;</a> <a href="profiling/functioncallcount.stp">profiling/functioncallcount.stp</a> - Count Times Functions Are Called 
keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> <a href="keyword-index.html#FUNCTION">FUNCTION</a> 
The functioncallcount.stp script takes one argument, a list of functions to probe. The script will run and count the number of times that each of the functions on the list is called. On exit the script will print a sorted list from most frequently to least frequently called function.<pre># stap -w functioncallcount.stp &quot;*@mm/*.c&quot; -T 1</pre>
</li><li><a name="profiling/ioctl_handler.stp"></a><a href="#profiling/ioctl_handler.stp">&para;</a> <a href="profiling/ioctl_handler.stp">profiling/ioctl_handler.stp</a> - Monitor which executables use ioctl syscalls and what kernel code is handling the ioctl 
keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> 
The ioctl systemcall is used to manipulate devices setting or special files. The way that ioctl syscalls are handled depend greatly on the device the special file is associated with. Using strace to monitor the open and ioctl syscalls may not give a good indication of what kernel code is actually handling the ioctl operations. The ioctl_handler.stp script is designed to provide more details. On exit the ioctl_handler.stp script provides a count of the ioctl syscalls for each executable run on the system. If there was some special device driver code used to handle to the ioctl, the output will have a tally of the times the function name and module was called for that executable. The &quot;--all-modules&quot; option should be included on the command line so the script can provide function name information.<pre># stap ioctl_handler.stp --all-modules -T 1</pre>
</li><li><a name="profiling/latencytap.stp"></a><a href="#profiling/latencytap.stp">&para;</a> <a href="profiling/latencytap.stp">profiling/latencytap.stp</a> - Show Reasons and Durations for Processes Sleeping 
keywords: <a href="keyword-index.html#_BEST">_BEST</a> <a href="keyword-index.html#PROFILING">PROFILING</a> 
The latencytap.stp script collects data on the intervals processes are deactivated (sleeping). The script categorizes the reasons for the sleeps by analyzing the backtraces and displays a sorted list of the top 20 causes from largest total sum time sleeping to smallest. The output is updated every 30 seconds. The script needs to be compiled with the &#39;--all-modules&#39; option to produce reasons for sleeps caused by modules. Optionally, this script can be used with the &#39;-c&#39; or &#39;-x&#39; options to focus on a specific PID.<a href="profiling/latencytap.txt">sample usage in profiling/latencytap.txt
</li><li><a name="profiling/linetimes.stp"></a><a href="#profiling/linetimes.stp">&para;</a> <a href="profiling/linetimes.stp">profiling/linetimes.stp</a> - Show Time Spent on Each Line of a Function 
keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> <a href="keyword-index.html#_BEST">_BEST</a> 
The linetimes.stp script takes two arguments: where to find the function and the function name. linetimes.stp will instrument each line in the function. It will print out the number of times that the function is called, a table with the average and maximum time each line takes, and control flow information when the script exits.<a href="profiling/linetimes.txt">sample usage in profiling/linetimes.txt
</li><li><a name="profiling/perf.stp"></a><a href="#profiling/perf.stp">&para;</a> <a href="profiling/perf.stp">profiling/perf.stp</a> - Show performance ratios using perf.counter to access performance counters 
keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> 
On exit the perf.stp script provides a sorted list showing cycles per insn, branches per insn, and cache refs per insn<pre># stap -w perf.stp -c &quot;find /usr/bin -name \&quot;l*\&quot; -printf \&quot;%h/%f %s %Cx \
%Ck%CM %Y\n\&quot;&quot;</pre>
</li><li><a name="profiling/periodic.stp"></a><a href="#profiling/periodic.stp">&para;</a> <a href="profiling/periodic.stp">profiling/periodic.stp</a> - Show the Period of the Various Timers on the System 
keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> 
The periodic.stp script uses the kernel.trace(&quot;timer_expire_entry&quot;) tracepoint to collect data on period and frequency of the various timers on the system. The script displays a sorted list of the timers observed on the system from most frequent to least frequent. The script needs to be compiled with the &#39;--all-modules&#39; option to produce list the function names. Optionally, this script can be used with a numerical argument to indicate the interval in seconds between printing output.<pre># stap periodic.stp --all-modules -T 1</pre>
</li><li><a name="profiling/pf2.stp"></a><a href="#profiling/pf2.stp">&para;</a> <a href="profiling/pf2.stp">profiling/pf2.stp</a> - Profile Kernel Functions 
keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> 
The pf2.stp script sets up time-based sampling. Every five seconds it prints out a sorted list with the top ten kernel functions with samples.<a href="profiling/pf2.txt">sample usage in profiling/pf2.txt
</li><li><a name="profiling/pf3.stp"></a><a href="#profiling/pf3.stp">&para;</a> <a href="profiling/pf3.stp">profiling/pf3.stp</a> - Profile Kernel/User Functions 
keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> 
The pf3.stp script sets up time-based sampling. Every five seconds it prints out a sorted list with the top twenty kernel and/or user functions with samples. Use any of --ldd, --all-modules, -d MODULE, -d /PATH/TO/EXEC to add more symbolic info.<a href="profiling/pf3.txt">sample usage in profiling/pf3.txt
</li><li><a name="profiling/pf4.stp"></a><a href="#profiling/pf4.stp">&para;</a> <a href="profiling/pf4.stp">profiling/pf4.stp</a> - Profile Kernel/User Backtraces 
keywords: <a href="keyword-index.html#_BEST">_BEST</a> <a href="keyword-index.html#PROFILING">PROFILING</a> <a href="keyword-index.html#BACKTRACE">BACKTRACE</a> 
The pf4.stp script sets up time-based sampling. Every five seconds it prints out a sorted list with the top twenty kernel and/or user stack backtraces (on a per-cpu basis). Use any of --ldd, --all-modules, -d MODULE, -d /PATH/TO/EXEC to add more symbolic info.<a href="profiling/pf4.txt">sample usage in profiling/pf4.txt
</li><li><a name="profiling/sched_switch.stp"></a><a href="#profiling/sched_switch.stp">&para;</a> <a href="profiling/sched_switch.stp">profiling/sched_switch.stp</a> - Display the Task Switches Happening in the Scheduler 
keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> <a href="keyword-index.html#FUNCTION">FUNCTION</a> 
The sched_switch.stp script takes two arguments, first argument can be &quot;pid&quot; or &quot;name&quot; to indicate what is being passed as second argument. The script will trace the process based on pid/name and print the scheduler switches happening with the process. If no arguments are passed, it displays all the scheduler switches. This can be used to understand which tasks schedule out the current process being traced, and when it gets scheduled in again.<pre># stap sched_switch.stp -T 1</pre>
</li><li><a name="profiling/syscallerrorsbypid.stp"></a><a href="#profiling/syscallerrorsbypid.stp">&para;</a> <a href="profiling/syscallerrorsbypid.stp">profiling/syscallerrorsbypid.stp</a> - Provide a per-process syscall error tally on the system 
keywords: <a href="keyword-index.html#PROMETHEUS">PROMETHEUS</a> <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#SYSCALL">SYSCALL</a> <a href="keyword-index.html#TRACEPOINT">TRACEPOINT</a> 
The syscallerrorsbypid.stp script tallies syscall errors for each running process. This information can be useful to whether there are excessive errors for various processes on the system. The script makes the information available via procfs in Prometheus readable format. When a process exits its data will be eliminated from the prometheus output. To avoid exceeding the storage limitations of SystemTap older entries maybe overwritten by newer entries. This can lead to some active process syscall error counts disappearing and/or later reappearing with a lower value. Also note that the script does not properly name syscalls for 32-bit applications running on 64-bit machines.<pre># stap syscallerrorsbypid.stp -T 1</pre>
</li><li><a name="profiling/syscalllatency.stp"></a><a href="#profiling/syscalllatency.stp">&para;</a> <a href="profiling/syscalllatency.stp">profiling/syscalllatency.stp</a> - Provide a per-process accumulation of syscall latency on the system 
keywords: <a href="keyword-index.html#PROMETHEUS">PROMETHEUS</a> <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#SYSCALL">SYSCALL</a> <a href="keyword-index.html#TRACEPOINT">TRACEPOINT</a> 
The syscalllatency.stp script accumulates syscall latency for each running process. This information can be useful to whether excessive time is being spent in particular syscalls on the system. The script makes the information available via procfs in Prometheus readable format. When a process exits its data will be eliminated from the prometheus output. To avoid exceeding the storage limitations of SystemTap older entries maybe overwritten by newer entries. This can lead to some active process syscall error counts disappearing and/or later reappearing with a lower value. Also note that the script does not properly name syscalls for 32-bit applications running on 64-bit machines.<pre># stap syscalllatency.stp -T 1</pre>
</li><li><a name="profiling/syscallsbypid.stp"></a><a href="#profiling/syscallsbypid.stp">&para;</a> <a href="profiling/syscallsbypid.stp">profiling/syscallsbypid.stp</a> - Provide a per-process syscall tally on the system 
keywords: <a href="keyword-index.html#PROMETHEUS">PROMETHEUS</a> <a href="keyword-index.html#PROCESS">PROCESS</a> <a href="keyword-index.html#SYSCALL">SYSCALL</a> <a href="keyword-index.html#TRACEPOINT">TRACEPOINT</a> 
The syscallsbypid.stp script tallies each syscall for each running process. This information can be useful to determine the activity of various processes on the system. The script makes the information available via procfs in Prometheus readable format. When a process exits its data will be eliminated from the prometheus output. To avoid exceeding the storage limitations of SystemTap older entries maybe overwritten by newer entries. This can lead to some active process syscall counts disappearing and/or later reappearing with a lower value. Also note that the script does not properly name syscalls for 32-bit applications running on 64-bit machines.<pre># stap syscallsbypid.stp -T 1</pre>
</li><li><a name="profiling/syscallsrw.stp"></a><a href="#profiling/syscallsrw.stp">&para;</a> <a href="profiling/syscallsrw.stp">profiling/syscallsrw.stp</a> - Provide a tally of read and write syscalls run on the system 
keywords: <a href="keyword-index.html#PROMETHEUS">PROMETHEUS</a> <a href="keyword-index.html#SYSCALL">SYSCALL</a> <a href="keyword-index.html#BPF">BPF</a> 
The syscallsrw.stp script tallies the read and write syscalls. This is a demo script for stapbpf prometheus-exporter scripts.
</li><li><a name="profiling/thread-times.stp"></a><a href="#profiling/thread-times.stp">&para;</a> <a href="profiling/thread-times.stp">profiling/thread-times.stp</a> - Profile Kernel Functions 
keywords: <a href="keyword-index.html#_BEST">_BEST</a> <a href="keyword-index.html#PROFILING">PROFILING</a> 
The thread-times.stp script sets up time-based sampling. Every five seconds it prints out a sorted list with the top twenty threads occupying the CPUs, broken down as a percentage of user and kernel time.<a href="profiling/thread-times.txt">sample usage in profiling/thread-times.txt
</li><li><a name="profiling/timeout.stp"></a><a href="#profiling/timeout.stp">&para;</a> <a href="profiling/timeout.stp">profiling/timeout.stp</a> - Show Processes Doing Polling Operations 
keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> 
The timeout.stp script is based on a blog entry (http://udrepper.livejournal.com/19041.html) mentioning a need for a tool to help developers find applications that are polling. The timeout.stp script monitors systemcall used for polling and records the systemcalls that timed out rather than returned because some action occurred. The script updates the screen once a second with the top twenty processes.<pre># stap timeout.stp -T 1</pre>
</li><li><a name="profiling/topsys.stp"></a><a href="#profiling/topsys.stp">&para;</a> <a href="profiling/topsys.stp">profiling/topsys.stp</a> - Show Processes Doing Polling Operations 
keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> 
 The topsys.stp script lists out the top twenty systemcalls for the previous 5 seconds. The output is sorted from most frequent to least frequent.<pre># stap topsys.stp -T 1</pre>
</li><li><a name="profiling/ucalls.stp"></a><a href="#profiling/ucalls.stp">&para;</a> <a href="profiling/ucalls.stp">profiling/ucalls.stp</a> - Profile method invocations in Java, Perl, Php, Python, Ruby, and Tcl scripts 
keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> <a href="keyword-index.html#SYSCALL">SYSCALL</a> 
The ucalls.stp script is modeled after the BCC ucalls script (https://github.com/iovisor/bcc/blob/master/tools/lib/ucalls.py) by Sasha Goldshtein. The ucalls.stp script monitors the process indicated by the -x or -c option. When the scripts exits it prints out information about the number of times that each method is invoked for code written in Java, Perl, Php, Python, Ruby, and Tcl. Include the word &quot;syscalls&quot; on the command line to count syscalls invoked by the process. If you want latency information, include &quot;latency&quot; on the command line. Note that the latency option does not work for recursive functions<pre># stap ucalls.stp syscalls latency -c &quot;python -c &#39;print(\&quot;hello world\&quot;)&#39; \
|| true&quot;</pre>
</li><li><a name="security-band-aids/cve-2008-0600.stp"></a><a href="#security-band-aids/cve-2008-0600.stp">&para;</a> <a href="security-band-aids/cve-2008-0600.stp">security-band-aids/cve-2008-0600.stp</a> - cve-2008-0600 security band-aid 
keywords: <a href="keyword-index.html#SECURITY">SECURITY</a> <a href="keyword-index.html#GURU">GURU</a> 
historical emergency security band-aid, for reference/education only<a href="security-band-aids/cve-2008-0600.txt">sample usage in security-band-aids/cve-2008-0600.txt
</li><li><a name="security-band-aids/cve-2011-4127.stp"></a><a href="#security-band-aids/cve-2011-4127.stp">&para;</a> <a href="security-band-aids/cve-2011-4127.stp">security-band-aids/cve-2011-4127.stp</a> - cve-2011-4127 security band-aid 
keywords: <a href="keyword-index.html#SECURITY">SECURITY</a> <a href="keyword-index.html#GURU">GURU</a> 
historical emergency security band-aid, for reference/education only
</li><li><a name="security-band-aids/cve-2012-0056.stp"></a><a href="#security-band-aids/cve-2012-0056.stp">&para;</a> <a href="security-band-aids/cve-2012-0056.stp">security-band-aids/cve-2012-0056.stp</a> - cve-2012-0056 security band-aid 
keywords: <a href="keyword-index.html#SECURITY">SECURITY</a> <a href="keyword-index.html#GURU">GURU</a> 
historical emergency security band-aid, for reference/education only
</li><li><a name="security-band-aids/cve-2013-2094.stp"></a><a href="#security-band-aids/cve-2013-2094.stp">&para;</a> <a href="security-band-aids/cve-2013-2094.stp">security-band-aids/cve-2013-2094.stp</a> - cve-2013-2094 security band-aid 
keywords: <a href="keyword-index.html#SECURITY">SECURITY</a> <a href="keyword-index.html#GURU">GURU</a> 
historical emergency security band-aid, for reference/education only
</li><li><a name="security-band-aids/cve-2014-7169.stp"></a><a href="#security-band-aids/cve-2014-7169.stp">&para;</a> <a href="security-band-aids/cve-2014-7169.stp">security-band-aids/cve-2014-7169.stp</a> - cve-2014-7169 security band-aid 
keywords: <a href="keyword-index.html#SECURITY">SECURITY</a> <a href="keyword-index.html#GURU">GURU</a> 
historical emergency security band-aid, for reference/education only
</li><li><a name="security-band-aids/cve-2015-0235.stp"></a><a href="#security-band-aids/cve-2015-0235.stp">&para;</a> <a href="security-band-aids/cve-2015-0235.stp">security-band-aids/cve-2015-0235.stp</a> - cve-2015-0235 security band-aid 
keywords: <a href="keyword-index.html#SECURITY">SECURITY</a> <a href="keyword-index.html#GURU">GURU</a> 
historical emergency security band-aid, for reference/education only
</li><li><a name="security-band-aids/cve-2015-3456.stp"></a><a href="#security-band-aids/cve-2015-3456.stp">&para;</a> <a href="security-band-aids/cve-2015-3456.stp">security-band-aids/cve-2015-3456.stp</a> - cve-2015-3456 security band-aid 
keywords: <a href="keyword-index.html#SECURITY">SECURITY</a> <a href="keyword-index.html#GURU">GURU</a> 
historical emergency security band-aid, for reference/education only
</li><li><a name="security-band-aids/cve-2015-7547.stp"></a><a href="#security-band-aids/cve-2015-7547.stp">&para;</a> <a href="security-band-aids/cve-2015-7547.stp">security-band-aids/cve-2015-7547.stp</a> - cve-2015-7547 security band-aid 
keywords: <a href="keyword-index.html#SECURITY">SECURITY</a> <a href="keyword-index.html#GURU">GURU</a> 
historical emergency security band-aid, for reference/education only
</li><li><a name="security-band-aids/cve-2016-0728.stp"></a><a href="#security-band-aids/cve-2016-0728.stp">&para;</a> <a href="security-band-aids/cve-2016-0728.stp">security-band-aids/cve-2016-0728.stp</a> - cve-2016-0728 security band-aid 
keywords: <a href="keyword-index.html#SECURITY">SECURITY</a> <a href="keyword-index.html#GURU">GURU</a> 
historical emergency security band-aid, for reference/education only
</li><li><a name="security-band-aids/cve-2016-5195.stp"></a><a href="#security-band-aids/cve-2016-5195.stp">&para;</a> <a href="security-band-aids/cve-2016-5195.stp">security-band-aids/cve-2016-5195.stp</a> - cve-2016-5195 security band-aid 
keywords: <a href="keyword-index.html#SECURITY">SECURITY</a> <a href="keyword-index.html#GURU">GURU</a> 
historical emergency security band-aid, for reference/education only
</li><li><a name="security-band-aids/cve-2017-6074.stp"></a><a href="#security-band-aids/cve-2017-6074.stp">&para;</a> <a href="security-band-aids/cve-2017-6074.stp">security-band-aids/cve-2017-6074.stp</a> - cve-2017-6074 security band-aid 
keywords: <a href="keyword-index.html#SECURITY">SECURITY</a> <a href="keyword-index.html#GURU">GURU</a> 
historical emergency security band-aid, for reference/education only
</li><li><a name="security-band-aids/cve-2018-1000001.stp"></a><a href="#security-band-aids/cve-2018-1000001.stp">&para;</a> <a href="security-band-aids/cve-2018-1000001.stp">security-band-aids/cve-2018-1000001.stp</a> - cve-2018-1000001 security band-aid 
keywords: <a href="keyword-index.html#SECURITY">SECURITY</a> <a href="keyword-index.html#GURU">GURU</a> 
historical emergency security band-aid, for reference/education only
</li><li><a name="security-band-aids/cve-2018-14634.stp"></a><a href="#security-band-aids/cve-2018-14634.stp">&para;</a> <a href="security-band-aids/cve-2018-14634.stp">security-band-aids/cve-2018-14634.stp</a> - cve-2018-14634 security band-aid 
keywords: <a href="keyword-index.html#SECURITY">SECURITY</a> <a href="keyword-index.html#GURU">GURU</a> 
historical emergency security band-aid, for reference/education only
</li><li><a name="security-band-aids/cve-2018-6485.stp"></a><a href="#security-band-aids/cve-2018-6485.stp">&para;</a> <a href="security-band-aids/cve-2018-6485.stp">security-band-aids/cve-2018-6485.stp</a> - cve-2018-6485 security band-aid 
keywords: <a href="keyword-index.html#SECURITY">SECURITY</a> <a href="keyword-index.html#GURU">GURU</a> 
historical emergency security band-aid, for reference/education only
</li><li><a name="security-band-aids/cve-2021-4034.stp"></a><a href="#security-band-aids/cve-2021-4034.stp">&para;</a> <a href="security-band-aids/cve-2021-4034.stp">security-band-aids/cve-2021-4034.stp</a> - cve-2021-4034 security band-aid 
keywords: <a href="keyword-index.html#SECURITY">SECURITY</a> <a href="keyword-index.html#GURU">GURU</a> 
historical emergency security band-aid, for reference/education only
</li><li><a name="security-band-aids/cve-2021-4155.stp"></a><a href="#security-band-aids/cve-2021-4155.stp">&para;</a> <a href="security-band-aids/cve-2021-4155.stp">security-band-aids/cve-2021-4155.stp</a> - cve-2021-4155 security band-aid 
keywords: <a href="keyword-index.html#SECURITY">SECURITY</a> <a href="keyword-index.html#GURU">GURU</a> 
historical emergency security band-aid, for reference/education only
</li><li><a name="stapgames/2048.stp"></a><a href="#stapgames/2048.stp">&para;</a> <a href="stapgames/2048.stp">stapgames/2048.stp</a> - 2048 
keywords: <a href="keyword-index.html#_BEST">_BEST</a> <a href="keyword-index.html#STAPGAMES">STAPGAMES</a> 
The modern classic 2048 sliding-tiles game, using local keyboard and ansi animation.<pre># stap -p4 2048.stp</pre>
</li><li><a name="stapgames/block.stp"></a><a href="#stapgames/block.stp">&para;</a> <a href="stapgames/block.stp">stapgames/block.stp</a> - block breaker game 
keywords: <a href="keyword-index.html#STAPGAMES">STAPGAMES</a> 
A block game where you progressively break the ceiling blocks until clearing the level<pre># stap -p4 -Itapset/ block.stp</pre>
</li><li><a name="stapgames/eater.stp"></a><a href="#stapgames/eater.stp">&para;</a> <a href="stapgames/eater.stp">stapgames/eater.stp</a> - eater game 
keywords: <a href="keyword-index.html#STAPGAMES">STAPGAMES</a> 
walk through a maze, eat stuff<pre># stap -p4 -Itapset/ eater.stp</pre>
</li><li><a name="stapgames/lifegame.stp"></a><a href="#stapgames/lifegame.stp">&para;</a> <a href="stapgames/lifegame.stp">stapgames/lifegame.stp</a> - life game 
keywords: <a href="keyword-index.html#STAPGAMES">STAPGAMES</a> 
watch as your creation morphes into different forms<pre># stap -p4 -Itapset/ lifegame.stp</pre>
</li><li><a name="stapgames/pingpong.stp"></a><a href="#stapgames/pingpong.stp">&para;</a> <a href="stapgames/pingpong.stp">stapgames/pingpong.stp</a> - pingpong game 
keywords: <a href="keyword-index.html#STAPGAMES">STAPGAMES</a> 
A simulated ball bounces around the terminal reflecting at the edges<pre># stap -p4 -Itapset/ pingpong.stp</pre>
</li><li><a name="virtualization/kvm_service_time.stp"></a><a href="#virtualization/kvm_service_time.stp">&para;</a> <a href="virtualization/kvm_service_time.stp">virtualization/kvm_service_time.stp</a> - Time Statistics on KVM Exit Reasons 
keywords: <a href="keyword-index.html#_BEST">_BEST</a> <a href="keyword-index.html#VIRTUALIZATION">VIRTUALIZATION</a> <a href="keyword-index.html#KVM">KVM</a> 
The kvm_service_time.stp script tracks the statistics about the amount of time that the processor left the guest virtual machine for each exit reason (for example fixing up a page table or handling an IO operation). When the script exits it prints out the number of times each exit reason was encountered, the total duration of time it left the guest VM, the minimum time, the average time, and the maximum time in microseconds for that exit reason. On Linux 2.6.38 and newer kernel the script can automatically determine whether it is running on Intel or AMD processors. For older kernels with a kernel.trace(&quot;kvm_exit&quot;) tracepoint that does not have the $isa parameter you can explicitly state the kvm type with a &quot;-G kvm=intel&quot; or &quot;-G kvm=amd&quot; on the command line.<a href="virtualization/kvm_service_time.txt">sample usage in virtualization/kvm_service_time.txt
</li><li><a name="virtualization/qemu_count.stp"></a><a href="#virtualization/qemu_count.stp">&para;</a> <a href="virtualization/qemu_count.stp">virtualization/qemu_count.stp</a> - Tally the Number of User-Space QEMU Events 
keywords: <a href="keyword-index.html#VIRTUALIZATION">VIRTUALIZATION</a> <a href="keyword-index.html#QEMU">QEMU</a> <a href="keyword-index.html#KVM">KVM</a> 
The qemu_count.stp script tallies the number of times each of the user-space qemu probepoints is encountered. When the script exits, it prints a list of the number of times each user-space qemu probepoint is encountered.<pre># stap qemu_count.stp -T 1</pre>
</li><li><a name="virtualization/qemu_io.stp"></a><a href="#virtualization/qemu_io.stp">&para;</a> <a href="virtualization/qemu_io.stp">virtualization/qemu_io.stp</a> - Tally the Number of User-Space QEMU IO on Each IO Port 
keywords: <a href="keyword-index.html#VIRTUALIZATION">VIRTUALIZATION</a> <a href="keyword-index.html#QEMU">QEMU</a> <a href="keyword-index.html#KVM">KVM</a> <a href="keyword-index.html#IO">IO</a> 
The qemu_io.stp script tallies the number of times each of the IO port on the guest virtual machines is touched by a input or output operation. When the script exits, it prints a count of the number of times each IO port read and written.<pre># stap qemu_io.stp -T 1</pre>
</li></ul>
 	</td>
 </tr>
 </table>
 </div>
 </div>

<table cellspacing="2" cellpadding="2" border="0" width="100%">
 <tr>
 <td align="center" class="footer"><a href=
	 "http://sourceware.org/systemtap">SystemTap</a></td>
 </tr>
 </table>
</body>
</html>

cmd: