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.7-99-gcfcab6c
Date: Fri, 09 Mar 2012 19:03:00 -0000	[thread overview]
Message-ID: <20120309190320.27903.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  cfcab6c7110a016fe108bbf4783b7c437a3a9708 (commit)
      from  3965e105b73e196ec4f9b15c0b192c59bb14a2f8 (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 cfcab6c7110a016fe108bbf4783b7c437a3a9708
Author: Josh Stone <jistone@redhat.com>
Date:   Fri Dec 9 09:24:31 2011 -0800

    Preliminary SDT semaphores with inode-uprobes
    
    This adds mmap tracking to our inode-uprobes client, so we may
    manipulate SDT semaphores as modules come and go.  It seems to work ok,
    though remaining sleepiness issues may need to be worked out in
    task_finder2.

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

Summary of changes:
 runtime/uprobes-inode.c |  402 +++++++++++++++++++++++++++++++++++++++++++----
 tapsets.cxx             |   98 ++++++++----
 2 files changed, 440 insertions(+), 60 deletions(-)


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


                 reply	other threads:[~2012-03-09 19:03 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=20120309190320.27903.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: 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).