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.8-147-gff811c3
Date: Tue, 07 Aug 2012 01:02:00 -0000	[thread overview]
Message-ID: <20120807010235.24606.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  ff811c3dcafe9892a6447cfc61303284c4dfb545 (commit)
      from  87eeec9407f8afa5af1037600272eebf0561e1d1 (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 ff811c3dcafe9892a6447cfc61303284c4dfb545
Author: Josh Stone <jistone@redhat.com>
Date:   Mon Aug 6 17:46:38 2012 -0700

    stapdyn: Enable map and stat types
    
    There are a lot of kernel-isms in the map code especially, and rather
    than try to rewrite all that, I've simply copied the necessary bits from
    the kernel.  The new pieces are mostly list and hash related.
    
    * runtime/dyninst/alloc.c (_stp_alloc_percpu): Needs to be zeroed.
    * runtime/dyninst/runtime.h: Add BITS_PER_LONG and stap_hash_seed.
      Also extract various bits copied from the kernel into new files.
    * runtime/dyninst/linux_types.h: Reused Linux type definitions.
    * runtime/dyninst/linux_defs.h: Other various reused Linux code.
    * runtime/dyninst/linux_hash.h: Direct copy of hashing from Linux.
    * runtime/dyninst/ilog2.h: Linux's ilog2(), but just for constants.
    * runtime/dyninst/probe_lock.h: Typedef rwlock_t on pthreads.
    * runtime/map.c: Don't need sym.c, and emulate ALIGN().
    * runtime/map.h: Locate ilog2, and fix NEED_MAP_LOCKS check.

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

Summary of changes:
 runtime/dyninst/alloc.c                     |    2 +-
 runtime/dyninst/ilog2.h                     |  109 +++++++++++++
 runtime/dyninst/{runtime.h => linux_defs.h} |  223 ++++++++++++++-------------
 runtime/dyninst/linux_hash.h                |   70 +++++++++
 runtime/dyninst/linux_types.h               |   33 ++++
 runtime/dyninst/probe_lock.h                |    8 +-
 runtime/dyninst/runtime.h                   |  185 +---------------------
 runtime/map.c                               |    5 +-
 runtime/map.h                               |    9 +-
 9 files changed, 349 insertions(+), 295 deletions(-)
 create mode 100644 runtime/dyninst/ilog2.h
 copy runtime/dyninst/{runtime.h => linux_defs.h} (58%)
 create mode 100644 runtime/dyninst/linux_hash.h
 create mode 100644 runtime/dyninst/linux_types.h


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


                 reply	other threads:[~2012-08-07  1:02 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=20120807010235.24606.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).