public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: dsmith@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.3-267-g47606e7 Date: Thu, 04 Nov 2010 21:31:00 -0000 [thread overview] Message-ID: <20101104213059.29194.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 47606e7e7dd43966d96f5b185d2a4de8c266ebe7 (commit) from 055e3b408aefb37a44c336af306f22c356fe321a (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 47606e7e7dd43966d96f5b185d2a4de8c266ebe7 Author: David Smith <dsmith@redhat.com> Date: Thu Nov 4 16:30:09 2010 -0500 Updated memory.stp, rpc.stp, task.stp, and vfs.stp for 2.6.36. * tapset/memory.stp (vm.oom_kill): Added oom_kill_process(). * tapset/rpc.stp (sunrpc.clnt.call_sync): Updated for 2.6.36. (sunrpc.clnt.call_async): Ditto. * tapset/task.stp (task_gid): Updated for 2.6.36 by defining and using task_gid(). (task_egid): Updated for 2.6.36 by defining and using task_egid(). * tapset/vfs.stp (_vfs.block_prepare_write): Update for 2.6.36 by using __block_write_begin() as an alternative to __block_prepare_write(). (_vfs.block_write_begin): Updated for 2.6.36. ----------------------------------------------------------------------- Summary of changes: tapset/memory.stp | 3 +- tapset/rpc.stp | 14 +++++++----- tapset/task.stp | 22 +++++++++----------- tapset/vfs.stp | 57 +++++++++++++++++++++++++++++++++++++--------------- 4 files changed, 60 insertions(+), 36 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-11-04 21:31 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=20101104213059.29194.qmail@sourceware.org \ --to=dsmith@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).