public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: jistone@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.0-60-gee89e81 Date: Fri, 02 Oct 2009 23:51:00 -0000 [thread overview] Message-ID: <20091002235150.23564.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 ee89e81c3f87c4eef2b677ed7e38092e3d2c5af9 (commit) via 0449af0365f19c246f6ce09dd93118a597f78949 (commit) via ae3072f460693e85962556bf0529a729c7d97bf6 (commit) from a8f5a3bf344f9b014c5adf8b5eada10d09f31219 (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 ee89e81c3f87c4eef2b677ed7e38092e3d2c5af9 Author: Josh Stone <jistone@redhat.com> Date: Fri Oct 2 16:50:18 2009 -0700 AUTHORS bump for Kiran commit 0449af0365f19c246f6ce09dd93118a597f78949 Author: Josh Stone <jistone@redhat.com> Date: Fri Oct 2 16:42:44 2009 -0700 Updates samples index for sched_switch commit ae3072f460693e85962556bf0529a729c7d97bf6 Author: Kiran Prakesh <kiran@linux.vnet.ibm.com> Date: Thu Oct 1 22:39:32 2009 +0530 Scheduler Tapset based on kernel tracepoints This patch adds kernel tracepoints based probes to the scheduler tapset along with the testcase, scheduler-test-tracepoints.stp and an example script, sched_switch.stp. Signed-off-by: Kiran Prakash <kiran@linux.vnet.ibm.com> Signed-off-by: Josh Stone <jistone@redhat.com> ----------------------------------------------------------------------- Summary of changes: AUTHORS | 1 + tapset/scheduler.stp | 353 +++++++++++++++++--- testsuite/buildok/scheduler-test-tracepoints.stp | 51 +++ testsuite/systemtap.examples/index.html | 3 + testsuite/systemtap.examples/index.txt | 12 + testsuite/systemtap.examples/keyword-index.html | 6 + testsuite/systemtap.examples/keyword-index.txt | 24 ++ .../systemtap.examples/profiling/sched_switch.meta | 14 + .../systemtap.examples/profiling/sched_switch.stp | 63 ++++ 9 files changed, 476 insertions(+), 51 deletions(-) create mode 100644 testsuite/buildok/scheduler-test-tracepoints.stp create mode 100644 testsuite/systemtap.examples/profiling/sched_switch.meta create mode 100755 testsuite/systemtap.examples/profiling/sched_switch.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2009-10-02 23:51 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=20091002235150.23564.qmail@sourceware.org \ --to=jistone@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).