public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: serhei@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.8-239-g44cfbe2
Date: Tue, 18 Sep 2012 13:57:00 -0000	[thread overview]
Message-ID: <20120918135700.5499.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  44cfbe258c8cdd0bf0a677e913e885a3f942cc37 (commit)
      from  e3fcef9b73ffada8fc950912a3b9643b23a89eca (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 44cfbe258c8cdd0bf0a677e913e885a3f942cc37
Author: Serguei Makarov <smakarov@redhat.com>
Date:   Mon Sep 17 18:03:31 2012 -0400

    PR6580: incremental unwinder with cache.
    
    Implements a cached unwinder, allowing most backtrace tapset functions
    to be implemented in terms of stack() without loss of performance.
    stack() calls can be made repeatedly and in any order, and they will
    use the results of a single unwind. (Works only with the DWARF
    unwinder).
    
    _stp_stack_kernel_print et. al. retain their prior behaviour,
    including a number of fallbacks not available to the incremental
    unwind. These fallbacks only emit backtrace strings, which can be
    tokenized on the tapset end as a last resort.
    
    * runtime/unwind/unwind.h -- define struct unwind_cache to store PCs
      obtained from unwinder.
    * runtime/common_probe_context.h -- include two sets of unwinder
      context and cache, one for user side, one for kernel.
    * tapsets.cxx -- probe prologue includes a small thing to mark
      the unwind caches as being in an uninitialized state.
    * runtime/stack.c -- incremental unwinder implementation.
    * runtime/stack-dwarf.c -- deleted. Code moved to stack.c since
      this is now the preferred unwind method.
    * tapset/linux/[u]context-symbols.stp -- change stack(), ustack()
      to directly call incremental unwinder.

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

Summary of changes:
 runtime/common_probe_context.h    |    5 +-
 runtime/stack-dwarf.c             |   98 -----------
 runtime/stack.c                   |  330 ++++++++++++++++++++++++++++++++-----
 runtime/unwind/unwind.h           |   14 ++
 tapset/linux/context-symbols.stp  |   13 ++-
 tapset/linux/ucontext-symbols.stp |   13 ++-
 tapsets.cxx                       |    5 +
 7 files changed, 335 insertions(+), 143 deletions(-)
 delete mode 100644 runtime/stack-dwarf.c


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


                 reply	other threads:[~2012-09-18 13:57 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=20120918135700.5499.qmail@sourceware.org \
    --to=serhei@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).