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-622-ge44cf9f
Date: Mon, 19 Dec 2011 20:29:00 -0000 [thread overview]
Message-ID: <20111219202955.1882.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 e44cf9f078d5180120a87d74b4b06c2daf0f5c1f (commit)
via 4bd99fcf903829c8d672b9ae4a05005f44832044 (commit)
from a1110d49010eb792eb127624097818b0ab5ebf72 (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 e44cf9f078d5180120a87d74b4b06c2daf0f5c1f
Author: William Cohen <wcohen@redhat.com>
Date: Fri Dec 16 14:47:00 2011 -0500
Add a test for the speculative.stp tapset
A simple test to make sure that the speculative.stp tapset can be compiled
and used.
commit 4bd99fcf903829c8d672b9ae4a05005f44832044
Author: William Cohen <wcohen@redhat.com>
Date: Fri Dec 16 13:40:01 2011 -0500
Add the speculative.stp tapset
The speculative.stp tapset allow one to speculative add things to
output buffers and then later commit or discard the information in the
buffers. Four functions in the tapset:
speculation() - function to give an id for speculative buffer
speculate() - add output to a speculative buffer
discard() - remove output for a speculative buffer
commit() - output data for a speculative buffer
-----------------------------------------------------------------------
Summary of changes:
doc/SystemTap_Tapset_Reference/tapsets.tmpl | 10 +++
tapset/speculative.stp | 80 ++++++++++++++++++++
testsuite/systemtap.speculate/speculate.c | 34 ++++++++
.../speculate.exp} | 16 +---
testsuite/systemtap.speculate/speculate.stp | 44 +++++++++++
5 files changed, 173 insertions(+), 11 deletions(-)
create mode 100644 tapset/speculative.stp
create mode 100644 testsuite/systemtap.speculate/speculate.c
copy testsuite/{systemtap.base/bz10078.exp => systemtap.speculate/speculate.exp} (63%)
create mode 100644 testsuite/systemtap.speculate/speculate.stp
hooks/post-receive
--
systemtap: system-wide probe/trace tool
reply other threads:[~2011-12-19 20:29 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=20111219202955.1882.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).