diff options
author | Frank Ch. Eigler <fche@elastic.org> | 2010-02-01 15:39:44 -0500 |
---|---|---|
committer | Frank Ch. Eigler <fche@elastic.org> | 2010-02-01 15:39:51 -0500 |
commit | f503d3c056dd8cba03e0cf58a260655225ffe0b4 (patch) | |
tree | d8dff88e3cc21b8868a0746e9145c0087d209025 | |
parent | 0b12a8cd2ea7700fa9b96930947b7844cca0aab9 (diff) | |
download | systemtap-steved-f503d3c056dd8cba03e0cf58a260655225ffe0b4.tar.gz systemtap-steved-f503d3c056dd8cba03e0cf58a260655225ffe0b4.tar.xz systemtap-steved-f503d3c056dd8cba03e0cf58a260655225ffe0b4.zip |
regen sample indexes
-rw-r--r-- | testsuite/systemtap.examples/index.html | 3 | ||||
-rw-r--r-- | testsuite/systemtap.examples/index.txt | 9 | ||||
-rw-r--r-- | testsuite/systemtap.examples/keyword-index.html | 3 | ||||
-rw-r--r-- | testsuite/systemtap.examples/keyword-index.txt | 9 |
4 files changed, 24 insertions, 0 deletions
diff --git a/testsuite/systemtap.examples/index.html b/testsuite/systemtap.examples/index.html index 5b4ef659..294c6991 100644 --- a/testsuite/systemtap.examples/index.html +++ b/testsuite/systemtap.examples/index.html @@ -211,6 +211,9 @@ keywords: <a href="keyword-index.html#SYSCALL">SYSCALL</a> <br> <li><a href="process/wait4time.stp">process/wait4time.stp</a> - Trace Time Spent in wait4 Syscalls<br> keywords: <a href="keyword-index.html#SYSCALL">SYSCALL</a> <a href="keyword-index.html#WAIT4">WAIT4</a> <br> <p>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 "wait4:" 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 "-1".</p></li> +<li><a href="profiling/fntimes.stp">profiling/fntimes.stp</a> - Show functions taking longer than usual<br> +keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> <br> +<p>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.</p></li> <li><a href="profiling/functioncallcount.stp">profiling/functioncallcount.stp</a> - Count Times Functions Called<br> keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> <a href="keyword-index.html#FUNCTIONS">FUNCTIONS</a> <br> <p>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.</p></li> diff --git a/testsuite/systemtap.examples/index.txt b/testsuite/systemtap.examples/index.txt index 48494841..ebcd17a3 100644 --- a/testsuite/systemtap.examples/index.txt +++ b/testsuite/systemtap.examples/index.txt @@ -526,6 +526,15 @@ keywords: syscall wait4 waiting for. If the waited for PID is not specified , it is "-1". +profiling/fntimes.stp - Show functions taking longer than usual +keywords: profiling + + 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. + + profiling/functioncallcount.stp - Count Times Functions Called keywords: profiling functions diff --git a/testsuite/systemtap.examples/keyword-index.html b/testsuite/systemtap.examples/keyword-index.html index c33c56ef..39d29031 100644 --- a/testsuite/systemtap.examples/keyword-index.html +++ b/testsuite/systemtap.examples/keyword-index.html @@ -333,6 +333,9 @@ keywords: <a href="keyword-index.html#IO">IO</a> <a href="keyword-index.html#PRO <li><a href="process/pf2.stp">process/pf2.stp</a> - Profile kernel functions<br> keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> <br> <p>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.</p></li> +<li><a href="profiling/fntimes.stp">profiling/fntimes.stp</a> - Show functions taking longer than usual<br> +keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> <br> +<p>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.</p></li> <li><a href="profiling/functioncallcount.stp">profiling/functioncallcount.stp</a> - Count Times Functions Called<br> keywords: <a href="keyword-index.html#PROFILING">PROFILING</a> <a href="keyword-index.html#FUNCTIONS">FUNCTIONS</a> <br> <p>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.</p></li> diff --git a/testsuite/systemtap.examples/keyword-index.txt b/testsuite/systemtap.examples/keyword-index.txt index 4a9d5ccb..96ad06bd 100644 --- a/testsuite/systemtap.examples/keyword-index.txt +++ b/testsuite/systemtap.examples/keyword-index.txt @@ -697,6 +697,15 @@ keywords: profiling samples. +profiling/fntimes.stp - Show functions taking longer than usual +keywords: profiling + + 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. + + profiling/functioncallcount.stp - Count Times Functions Called keywords: profiling functions |