public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: wcohen@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-700-g1345075
Date: Tue, 31 Jan 2012 17:18:00 -0000 [thread overview]
Message-ID: <20120131171825.2354.qmail@sourceware.org> (raw)
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "systemtap: system-wide probe/trace tool".
The branch, master has been updated
via 1345075ddd23dbf3f7c03fd9d09e6dd6e80be5ae (commit)
via d37d33d5dbcf90aa25a97d880a4e8b0c716776c3 (commit)
via 082be5d88d4a02c5841d26d452545452c3a244a1 (commit)
from 0ba354fef113008daa4f52925a35fb4f9d8954ba (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 1345075ddd23dbf3f7c03fd9d09e6dd6e80be5ae
Author: William Cohen <wcohen@redhat.com>
Date: Tue Jan 31 11:53:51 2012 -0500
Updates the example indices.
commit d37d33d5dbcf90aa25a97d880a4e8b0c716776c3
Author: William Cohen <wcohen@redhat.com>
Date: Tue Jan 31 11:51:36 2012 -0500
Add example and buildok test for stopwatch.stp tapset
commit 082be5d88d4a02c5841d26d452545452c3a244a1
Author: William Cohen <wcohen@redhat.com>
Date: Tue Jan 31 10:50:53 2012 -0500
Add the stopwatch.stp tapset
The stopwatch.stp tapset provides multiple, independent timers to user
scripts. Stopwatches can be created by the user script at
anytime. The created stopwatches can be stopped and started by the
user script. The times from the stopwatches can be read in seconds,
milliseconds, microsecons, and nanoseconds.
Signed-off-by: William Cohen <wcohen@redhat.com>
-----------------------------------------------------------------------
Summary of changes:
doc/SystemTap_Tapset_Reference/tapsets.tmpl | 1 +
tapset/stopwatch.stp | 126 ++++++++++++++++++++
testsuite/buildok/stopwatches.stp | 67 +++++++++++
.../systemtap.examples/general/stopwatches.meta | 13 ++
.../systemtap.examples/general/stopwatches.stp | 45 +++++++
testsuite/systemtap.examples/index.html | 3 +
testsuite/systemtap.examples/index.txt | 14 ++
testsuite/systemtap.examples/keyword-index.html | 5 +-
testsuite/systemtap.examples/keyword-index.txt | 14 ++
9 files changed, 287 insertions(+), 1 deletions(-)
create mode 100644 tapset/stopwatch.stp
create mode 100755 testsuite/buildok/stopwatches.stp
create mode 100644 testsuite/systemtap.examples/general/stopwatches.meta
create mode 100644 testsuite/systemtap.examples/general/stopwatches.stp
hooks/post-receive
--
systemtap: system-wide probe/trace tool
reply other threads:[~2012-01-31 17:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120131171825.2354.qmail@sourceware.org \
--to=wcohen@sourceware.org \
--cc=systemtap-cvs@sourceware.org \
--cc=systemtap@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).