summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMark Wielaard <mwielaard@redhat.com>2008-08-11 17:04:36 +0200
committerMark Wielaard <mwielaard@redhat.com>2008-08-11 17:04:36 +0200
commit42f543d05a6f441bb212bd94f9ff44b4095f20dd (patch)
tree06ef9e779b91087ab6d4d45155971d9953b86c3d
parenta81c61ac1947cb5c13d3a758fc793a119b88b4e0 (diff)
downloadsystemtap-steved-42f543d05a6f441bb212bd94f9ff44b4095f20dd.tar.gz
systemtap-steved-42f543d05a6f441bb212bd94f9ff44b4095f20dd.tar.xz
systemtap-steved-42f543d05a6f441bb212bd94f9ff44b4095f20dd.zip
PR6835. io/io_submit.stp: Fix #! start. Convert to normal line-ending.
-rw-r--r--testsuite/systemtap.examples/ChangeLog5
-rwxr-xr-xtestsuite/systemtap.examples/io/io_submit.stp142
2 files changed, 76 insertions, 71 deletions
diff --git a/testsuite/systemtap.examples/ChangeLog b/testsuite/systemtap.examples/ChangeLog
index e2389993..c50bcefc 100644
--- a/testsuite/systemtap.examples/ChangeLog
+++ b/testsuite/systemtap.examples/ChangeLog
@@ -1,5 +1,10 @@
2008-08-11 Mark Wielaard <mwielaard@redhat.com>
+ PR6835. Reported by Eugeniy Meshcheryakov <eugen@debian.org>
+ * io/io_submit.stp: Fix #! start. Convert to normal line-ending.
+
+2008-08-11 Mark Wielaard <mwielaard@redhat.com>
+
PR2895. Reported by Eugeniy Meshcheryakov <eugen@debian.org>
* general/graphs.stp: Add proper #! /usr/bin/env stap line.
* general/para-callgraph.stp: Likewise.
diff --git a/testsuite/systemtap.examples/io/io_submit.stp b/testsuite/systemtap.examples/io/io_submit.stp
index 7f350305..13dcc5a3 100755
--- a/testsuite/systemtap.examples/io/io_submit.stp
+++ b/testsuite/systemtap.examples/io/io_submit.stp
@@ -1,71 +1,71 @@
-#! /bin/env stap
-#
-# Copyright (C) 2007 Oracle Corp. Chris Mason <chris.mason@oracle.com>
-#
-# This was implemented to find the most common causes of schedule during
-# the AIO io_submit call. It does this by recording which pids are inside
-# AIO, and recording the current stack trace if one of those pids is
-# inside schedule.
-# When the probe exits, it prints out the 30 most common call stacks for
-# schedule().
-#
-# This file is free software. You can redistribute it and/or modify it under
-# the terms of the GNU General Public License (GPL); either version 2, or (at
-# your option) any later version.
-
-global in_iosubmit
-global traces
-
-/*
- * add a probe to sys_io_submit, on entry, record in the in_iosubmit
- * hash table that this proc is in io_submit
- */
-probe syscall.io_submit {
- in_iosubmit[tid()] = 1
-}
-
-/*
- * when we return from sys_io_submit, record that we're no longer there
- */
-probe syscall.io_submit.return {
- /* this assumes a given proc will do lots of io_submit calls, and
- * so doesn't do the more expensive "delete in_iosubmit[p]". If
- * there are lots of procs doing small number of io_submit calls,
- * the hash may grow pretty big, so using delete may be better
- */
- in_iosubmit[tid()] = 0
-}
-
-/*
- * every time we call schedule, check to see if we started off in
- * io_submit. If so, record our backtrace into the traces histogram
- */
-probe kernel.function("schedule") {
- if (tid() in in_iosubmit) {
- traces[backtrace()]++
-
- /*
- * change this to if (1) if you want a backtrace every time
- * you go into schedule from io_submit. Unfortunately, the traces
- * saved into the traces histogram above are truncated to just a
- * few lines. so the only way to see the full trace is via the
- * more verbose print_backtrace() right here.
- */
- if (0) {
- printf("schedule in io_submit!\n")
- print_backtrace()
- }
- }
-}
-
-/*
- * when stap is done (via ctrl-c) go through the record of all the
- * trace paths and print the 30 most common.
- */
-probe end {
- foreach (stack in traces- limit 30) {
- printf("%d:", traces[stack])
- print_stack(stack);
- }
-}
-
+#! /usr/bin/env stap
+#
+# Copyright (C) 2007 Oracle Corp. Chris Mason <chris.mason@oracle.com>
+#
+# This was implemented to find the most common causes of schedule during
+# the AIO io_submit call. It does this by recording which pids are inside
+# AIO, and recording the current stack trace if one of those pids is
+# inside schedule.
+# When the probe exits, it prints out the 30 most common call stacks for
+# schedule().
+#
+# This file is free software. You can redistribute it and/or modify it under
+# the terms of the GNU General Public License (GPL); either version 2, or (at
+# your option) any later version.
+
+global in_iosubmit
+global traces
+
+/*
+ * add a probe to sys_io_submit, on entry, record in the in_iosubmit
+ * hash table that this proc is in io_submit
+ */
+probe syscall.io_submit {
+ in_iosubmit[tid()] = 1
+}
+
+/*
+ * when we return from sys_io_submit, record that we're no longer there
+ */
+probe syscall.io_submit.return {
+ /* this assumes a given proc will do lots of io_submit calls, and
+ * so doesn't do the more expensive "delete in_iosubmit[p]". If
+ * there are lots of procs doing small number of io_submit calls,
+ * the hash may grow pretty big, so using delete may be better
+ */
+ in_iosubmit[tid()] = 0
+}
+
+/*
+ * every time we call schedule, check to see if we started off in
+ * io_submit. If so, record our backtrace into the traces histogram
+ */
+probe kernel.function("schedule") {
+ if (tid() in in_iosubmit) {
+ traces[backtrace()]++
+
+ /*
+ * change this to if (1) if you want a backtrace every time
+ * you go into schedule from io_submit. Unfortunately, the traces
+ * saved into the traces histogram above are truncated to just a
+ * few lines. so the only way to see the full trace is via the
+ * more verbose print_backtrace() right here.
+ */
+ if (0) {
+ printf("schedule in io_submit!\n")
+ print_backtrace()
+ }
+ }
+}
+
+/*
+ * when stap is done (via ctrl-c) go through the record of all the
+ * trace paths and print the 30 most common.
+ */
+probe end {
+ foreach (stack in traces- limit 30) {
+ printf("%d:", traces[stack])
+ print_stack(stack);
+ }
+}
+