public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: mark@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-185-gcde9152
Date: Thu, 08 Sep 2011 17:02:00 -0000	[thread overview]
Message-ID: <20110908170240.5427.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  cde915281007248e7f11e1e49c17b5a61df27f8b (commit)
       via  40c2a13dc1d559e969bc7f1cd0fab8155edaa0d3 (commit)
       via  a4a98791f6659a59f26142b72298fc964faaf074 (commit)
       via  74a633228edc34e14121cec237ec447402178186 (commit)
       via  92c25572b09ea782ec9d0ce634531923ce945c04 (commit)
      from  e37a160cf90dc9e194687f6a983b018dc90d650a (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 cde915281007248e7f11e1e49c17b5a61df27f8b
Merge: 40c2a13 e37a160
Author: Mark Wielaard <mjw@redhat.com>
Date:   Thu Sep 8 17:34:29 2011 +0200

    Merge branch 'master' of ssh://sourceware.org/git/systemtap

commit 40c2a13dc1d559e969bc7f1cd0fab8155edaa0d3
Author: Mark Wielaard <mjw@redhat.com>
Date:   Thu Sep 8 17:30:59 2011 +0200

    Remove kfail from backtrace.exp. Fixed by commit 207d2d.

commit a4a98791f6659a59f26142b72298fc964faaf074
Author: Mark Wielaard <mjw@redhat.com>
Date:   Thu Sep 8 17:22:25 2011 +0200

    Remove commented out and outdated (confusing embedded C) example from SBG.
    
    Just remove so there are no false positives while looking for dangerous
    embedded C snippets. The actual example just includes the thread-times.stp
    file which is fine.

commit 74a633228edc34e14121cec237ec447402178186
Author: Mark Wielaard <mjw@redhat.com>
Date:   Thu Sep 8 17:14:32 2011 +0200

    Don't try to be smart detecting perf event was in user mode.
    
    Just use user_mode(regs) always.
    Add test to check we always detect some user_mode activity.

commit 92c25572b09ea782ec9d0ce634531923ce945c04
Author: Mark Wielaard <mjw@redhat.com>
Date:   Thu Sep 8 13:57:21 2011 +0200

    Rename CONTEXT regflags to probe_flags. Now simply indicates user mode.
    
    Renamed common_probe_context.h regflags to probe_flags, rename constant
    from _STP_REGS_USER_FLAG to _STP_PROBE_STATE_USER_MODE and use throughout
    tapsets to check whether in user_mode() or not.

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

Summary of changes:
 .../en-US/Useful_Scripts-threadtimes.xml           |   52 --------------------
 runtime/common_probe_context.h                     |    7 ++-
 runtime/regs.h                                     |    4 --
 runtime/runtime_defines.h                          |    5 ++
 runtime/stack.c                                    |    5 +-
 tapset-itrace.cxx                                  |    2 +-
 tapset-perfmon.cxx                                 |    8 +--
 tapset-timers.cxx                                  |    2 +-
 tapset-utrace.cxx                                  |    2 +-
 tapset/arm/registers.stp                           |    6 +-
 tapset/context-symbols.stp                         |    4 +-
 tapset/context.stp                                 |    7 +--
 tapset/i386/registers.stp                          |    6 +-
 tapset/s390/registers.stp                          |    6 +-
 tapset/utrace.stp                                  |    9 ++-
 tapsets.cxx                                        |    6 +-
 testsuite/systemtap.base/backtrace.exp             |    4 --
 testsuite/systemtap.base/pt_user_mode.exp          |   10 ++++
 testsuite/systemtap.base/pt_user_mode.stp          |   28 +++++++++++
 19 files changed, 77 insertions(+), 96 deletions(-)
 create mode 100644 testsuite/systemtap.base/pt_user_mode.exp
 create mode 100644 testsuite/systemtap.base/pt_user_mode.stp


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


                 reply	other threads:[~2011-09-08 17: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=20110908170240.5427.qmail@sourceware.org \
    --to=mark@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).