public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: mark@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.0-69-g47f0251
Date: Tue, 06 Oct 2009 17:25:00 -0000	[thread overview]
Message-ID: <20091006172510.9783.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  47f025139d1c2e75781cdab40dc9195396133754 (commit)
      from  2155081e1d9888cf57334bc57abb3fff9b49d8e1 (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 47f025139d1c2e75781cdab40dc9195396133754
Author: Mark Wielaard <mjw@redhat.com>
Date:   Tue Oct 6 19:24:22 2009 +0200

    Add proc_mem tapset, functions to query memory usage of the current process.
    
    * tapset/proc_mem.stp: New tapset.
    * testsuite/buildok/proc_mem.stp
    * doc/SystemTap_Tapset_Reference/tapsets.tmpl (memory_stp): Include
      tapset/proc_mem.stp.

-----------------------------------------------------------------------

Summary of changes:
 doc/SystemTap_Tapset_Reference/tapsets.tmpl |    4 +-
 tapset/proc_mem.stp                         |  194 +++++++++++++++++++++++++++
 testsuite/buildok/proc_mem.stp              |   13 ++
 3 files changed, 210 insertions(+), 1 deletions(-)
 create mode 100644 tapset/proc_mem.stp
 create mode 100755 testsuite/buildok/proc_mem.stp


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2009-10-06 17:25 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=20091006172510.9783.qmail@sourceware.org \
    --to=mark@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).