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-0.9.7-152-g29e2616
Date: Wed, 20 May 2009 21:57:00 -0000	[thread overview]
Message-ID: <20090520215729.8207.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  29e2616aeeb82605a6efe1dbc574b499781eafbe (commit)
      from  7872a5b9d76dc78d8956de3d2a11757783121674 (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 29e2616aeeb82605a6efe1dbc574b499781eafbe
Author: Josh Stone <jistone@redhat.com>
Date:   Wed May 20 14:46:25 2009 -0700

    PR10177: init/kill time in sleepy context only
    
    Previously, _stp_init_time and _stp_kill_time were being called from
    begin/end/error probes, which will run with preemption disabled.  The
    BUG reported on RT kernels showed that cpufreq_unregister_notifier can
    end up sleeping, which violates our preemption block.
    
    This patch moves the init/kill into systemtap_module_init/exit, where it
    is safe to sleep.  The code maintains a new predicate with the define
    STAP_NEED_GETTIMEOFDAY, so we don't still incur any timer overhead if
    it's not used.

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

Summary of changes:
 tapset/timestamp_gtod.stp              |   17 ++---------------
 testsuite/buildok/gtod_init.stp        |   13 +++++++++++++
 testsuite/buildok/gtod_noinit.stp      |   13 +++++++++++++
 testsuite/systemtap.base/gtod_init.exp |   29 -----------------------------
 translate.cxx                          |   14 ++++++++++++++
 5 files changed, 42 insertions(+), 44 deletions(-)
 create mode 100755 testsuite/buildok/gtod_init.stp
 create mode 100755 testsuite/buildok/gtod_noinit.stp
 delete mode 100644 testsuite/systemtap.base/gtod_init.exp


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


                 reply	other threads:[~2009-05-20 21: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=20090520215729.8207.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).