public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: fche@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-0.9.9-384-g8faa1fc
Date: Sat, 19 Sep 2009 01:40:00 -0000	[thread overview]
Message-ID: <20090919014038.21630.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  8faa1fc5f98ccb87beb2e71c0ce087278a950dde (commit)
      from  ba01c24c38c098ae93cf62b239f03e824b5f5600 (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 8faa1fc5f98ccb87beb2e71c0ce087278a950dde
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Fri Sep 18 21:31:06 2009 -0400

    PR10655 part 1: uprobes: track sdt semaphores properly
    
    commit 6846cfc8 introduced an unintended side-effect where semaphore tracking
    was identified with stap_uprobe_specs[] elements, which are normally static/const.
    This kernel patch <http://article.gmane.org/gmane.linux.kernel/854187> catches
    and panics on this.  The cure is to move the variable over to the stap_uprobes[]
    array.
    
    * tapsets.cxx (uprobe emit_module_decls): Add sdt_sem_address to stap_uprobe{} struct,
      to contain per-process relocated semaphore address.
      (emit_module_decls,_init): Remove tsk field, restore constness of appropriate
      locals.  Activate uprobe semaphore right around uprobe activation time.  Remove
      semaphore clearing upon process exit, since by then it's gone.
      (emit_module_exit): Use remembered relocated semaphore address to clean up.
      Fix "-uprobe" DEBUG_UPROBES message.
    * runtime.h: #include <linux/sched.h>.
    * dtrace.in (*_semaphore): Make it an unsigned short - intended 16 bits on all
      common architectures/multilibs.

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

Summary of changes:
 dtrace.in         |    6 ++-
 runtime/runtime.h |    1 +
 tapsets.cxx       |   82 ++++++++++++++++++++++++++++++----------------------
 3 files changed, 52 insertions(+), 37 deletions(-)


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


                 reply	other threads:[~2009-09-19  1:40 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=20090919014038.21630.qmail@sourceware.org \
    --to=fche@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).