public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: serhei@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.8-31-g2f5bbff
Date: Thu, 28 Jun 2012 21:24:00 -0000 [thread overview]
Message-ID: <20120628212400.1621.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 2f5bbffa204e086143db19241c46be0c06277944 (commit)
via 80c18fb07e4c0024ff14f699026a33aa89fb05c5 (commit)
via 8eb6206cd38c487171bbbbd1bb9117891d2d6978 (commit)
from 33631d57fcf18c3981b83d786b01573cf1a7cf9c (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 2f5bbffa204e086143db19241c46be0c06277944
Author: Serguei Makarov <smakarov@redhat.com>
Date: Thu Jun 28 17:23:34 2012 -0400
PR12210: documentation and examples for alias suffix enhancement.
commit 80c18fb07e4c0024ff14f699026a33aa89fb05c5
Author: Serguei Makarov <smakarov@redhat.com>
Date: Thu Jun 28 17:18:41 2012 -0400
PR12210: testsuite for alias suffix enhancement.
commit 8eb6206cd38c487171bbbbd1bb9117891d2d6978
Author: Serguei Makarov <smakarov@redhat.com>
Date: Thu Jun 28 17:07:01 2012 -0400
PR12210: Basic implementation of alias suffixes.
This enhancement permits the script writer to attach a suffix when
invoking a probe alias. The components in the suffix are passed on
to the underlying probe point.
e.g. syscall.read.maxactive(10) expands to something like
kernel.function("sys_read").return.maxactive(10); the
maxactive(10) part is a suffix that is attached to the
alias expansion of syscall.read.return.
At this stage, the interaction of the feature with wildcards
is somewhat limited. Namely, alias suffixes appear in wildcard
expansions only when the old implementation would signal an
error due to lack of expansions (see documentation in the next
commit for details). This minimizes the impact on existing code,
but the restriction should be removed as soon as we figure out
a way to make the available suffixes reliably discoverable in
error messages, features such as stap -l, etc.
-----------------------------------------------------------------------
Summary of changes:
doc/langref.tex | 44 ++++
elaborate.cxx | 228 +++++++++++++++++---
elaborate.h | 35 +++-
main.cxx | 8 +-
stapprobes.3stap | 19 ++-
staptree.h | 1 +
testsuite/buildok/alias_suffixes01.stp | 7 +
testsuite/buildok/alias_suffixes02.stp | 3 +
testsuite/buildok/alias_suffixes03.stp | 7 +
testsuite/buildok/alias_suffixes04.stp | 8 +
testsuite/buildok/alias_suffixes05.stp | 7 +
testsuite/buildok/alias_suffixes06.stp | 7 +
testsuite/semko/alias_suffixes01.stp | 11 +
testsuite/semko/alias_suffixes02.stp | 8 +
testsuite/semko/alias_suffixes03.stp | 11 +
testsuite/semko/alias_suffixes04.stp | 5 +
testsuite/semko/alias_suffixes05.stp | 5 +
testsuite/semko/alias_suffixes06.stp | 10 +
testsuite/semko/alias_suffixes07.stp | 7 +
testsuite/systemtap.base/alias_suffixes.exp | 5 +
testsuite/systemtap.base/alias_suffixes01.stp | 13 ++
testsuite/systemtap.base/alias_suffixes02.stp | 19 ++
testsuite/systemtap.base/alias_suffixes03.stp | 18 ++
testsuite/systemtap.base/alias_suffixes04.stp | 13 ++
testsuite/systemtap.base/alias_suffixes05.stp | 17 ++
.../systemtap.examples/general/alias_suffixes.meta | 10 +
.../systemtap.examples/general/alias_suffixes.stp | 29 +++
27 files changed, 521 insertions(+), 34 deletions(-)
create mode 100755 testsuite/buildok/alias_suffixes01.stp
create mode 100755 testsuite/buildok/alias_suffixes02.stp
create mode 100755 testsuite/buildok/alias_suffixes03.stp
create mode 100755 testsuite/buildok/alias_suffixes04.stp
create mode 100755 testsuite/buildok/alias_suffixes05.stp
create mode 100755 testsuite/buildok/alias_suffixes06.stp
create mode 100755 testsuite/semko/alias_suffixes01.stp
create mode 100755 testsuite/semko/alias_suffixes02.stp
create mode 100755 testsuite/semko/alias_suffixes03.stp
create mode 100755 testsuite/semko/alias_suffixes04.stp
create mode 100755 testsuite/semko/alias_suffixes05.stp
create mode 100755 testsuite/semko/alias_suffixes06.stp
create mode 100755 testsuite/semko/alias_suffixes07.stp
create mode 100644 testsuite/systemtap.base/alias_suffixes.exp
create mode 100644 testsuite/systemtap.base/alias_suffixes01.stp
create mode 100644 testsuite/systemtap.base/alias_suffixes02.stp
create mode 100644 testsuite/systemtap.base/alias_suffixes03.stp
create mode 100644 testsuite/systemtap.base/alias_suffixes04.stp
create mode 100644 testsuite/systemtap.base/alias_suffixes05.stp
create mode 100644 testsuite/systemtap.examples/general/alias_suffixes.meta
create mode 100644 testsuite/systemtap.examples/general/alias_suffixes.stp
hooks/post-receive
--
systemtap: system-wide probe/trace tool
reply other threads:[~2012-06-28 21:24 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=20120628212400.1621.qmail@sourceware.org \
--to=serhei@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).