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-81-g0670efc Date: Sat, 10 Oct 2009 09:47:00 -0000 [thread overview] Message-ID: <20091010094740.17712.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 0670efc6debceea57084547976c229335cc0e2fd (commit) via eb5363b8f07d51caeb263c6a686c9a2556aa4c05 (commit) from e34d5d1388d3c7817313685e3f7424ffc158474f (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 0670efc6debceea57084547976c229335cc0e2fd Author: Mark Wielaard <mjw@redhat.com> Date: Fri Oct 9 23:23:12 2009 +0200 Add task_time tapset, functions to query time resource usage of current task. * tapset/task_time.stp: New tapset. * testsuite/buildok/task_test.stp: Add new task_time functions. * doc/SystemTap_Tapset_Reference/tapsets.tmpl: Add new section on Task Time Tapset. Include tapset/task_time.stp. commit eb5363b8f07d51caeb263c6a686c9a2556aa4c05 Author: Mark Wielaard <mjw@redhat.com> Date: Fri Oct 9 14:31:18 2009 +0200 tapset/proc_mem.stp: Document function parameters. ----------------------------------------------------------------------- Summary of changes: doc/SystemTap_Tapset_Reference/tapsets.tmpl | 10 +++ tapset/proc_mem.stp | 2 + tapset/task_time.stp | 101 +++++++++++++++++++++++++++ testsuite/buildok/task_test.stp | 8 ++ 4 files changed, 121 insertions(+), 0 deletions(-) create mode 100644 tapset/task_time.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2009-10-10 9:47 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=20091010094740.17712.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: linkBe 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).