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.3-174-gc87ae2c
Date: Sat, 02 Oct 2010 02:19:00 -0000	[thread overview]
Message-ID: <20101002021934.31252.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  c87ae2c195e2c0e8d22cdc2c3f767834d605ed90 (commit)
       via  26e6367359476da839ab1ed7abcc4b52925da649 (commit)
      from  86229a5533de13b6ac6eeb34d9ea24e7cfb64faa (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 c87ae2c195e2c0e8d22cdc2c3f767834d605ed90
Author: Josh Stone <jistone@redhat.com>
Date:   Fri Oct 1 16:41:19 2010 -0700

    Replace kretprobe->entry_ph with a full stap_probe
    
    This ensures that pp, pn, and STP_TIMING can be kept distinct for entry
    handlers vs. their normal kretprobe handlers.
    
    * tapsets.cxx (dwarf_derived_probe_group::emit_module_decls): Replace
      entry_ph with entry_probe, pointing to the global stap_probes[], and
      update all references.

commit 26e6367359476da839ab1ed7abcc4b52925da649
Author: Josh Stone <jistone@redhat.com>
Date:   Fri Oct 1 15:47:45 2010 -0700

    Centralize stap_probe, and make STP_TIMING data-driven
    
    With the move to per-probe_point STP_TIMING statistics, the design which
    wrote a separate code block for every Stat suddenly ran into scalability
    issues.  We should instead be using a data-driven loop for this.
    
    So, the scattered stap_probe structs are now pulled together in one
    global, stap_probes[].  This contains the usual suspects: ph, pp, and pn;
    it also keeps the extras that STP_TIMING needs: a Stat, the script
    location, and the derivation record.
    
    * translate.cxx (translate_pass): Add the STP_TIMING data to stap_probe,
      and output the global stap_probes[] with everything.
      (c_unparser::emit_module_init): Iterate the timing init at runtime.
      (c_unparser::emit_module_exit): Iterate the timing output at runtime.
    * tapsets.cxx (common_probe_init): Just return the right global stap_probe*
    * tapset*.cxx, runtime/*: Make pointers of all stap_probe's, and make
      the s/\./->/ change where needed too.
    * elaborate.cxx (derived_probe::derived_locations): New, gives a string
      reporting the derivation steps which reached this probe point.

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

Summary of changes:
 elaborate.cxx            |   14 +++++-
 elaborate.h              |    5 ++-
 runtime/perf.h           |    2 +-
 runtime/procfs-probes.c  |    8 ++--
 runtime/uprobes-common.c |    8 ++--
 runtime/uprobes-common.h |    2 +-
 tapset-been.cxx          |    4 +-
 tapset-itrace.cxx        |    4 +-
 tapset-mark.cxx          |    6 +-
 tapset-perfmon.cxx       |    4 +-
 tapset-procfs.cxx        |   10 ++--
 tapset-timers.cxx        |   25 +++++-----
 tapset-utrace.cxx        |    8 ++--
 tapsets.cxx              |   89 ++++++++++++++++------------------
 translate.cxx            |  122 ++++++++++++++++++---------------------------
 15 files changed, 149 insertions(+), 162 deletions(-)


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


                 reply	other threads:[~2010-10-02  2:19 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=20101002021934.31252.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).