public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: fche@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.2-50-gbf17a5d
Date: Sat, 10 Apr 2010 11:10:00 -0000	[thread overview]
Message-ID: <20100410111000.9226.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  bf17a5d2c707e8cd031d2a1dba2709b50452ba0c (commit)
       via  2fd5495a269c9995bd5789079dc9cbd65bd23f9e (commit)
      from  db135493669e5e2e1d0dc5c30c8d4a38bfd6653f (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 bf17a5d2c707e8cd031d2a1dba2709b50452ba0c
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Fri Apr 9 21:12:56 2010 -0400

    runtime: switch to deferred STP_EXIT signalling
    
    The former code allowed stapio to have two concurrent commands sent
    toward the runtime at the same time: one from the main loop and
    another one from the signal handling thread.  This is suspected to
    have caused occasional lockups.  This new code switches to a deferred
    signal handling model, where the signal handling thread merely
    increments a counter, and the main loop monitors that count.
    Unfortunately, this currently involves switching the main loop's
    blocking /.ctl read into a nonblocking poll.
    
    * runtime/staprun/mainloop.c (pending_interrupts): New variable.
      (signal_thread): Increment it.
      (stp_main_loop): Check it.

commit 2fd5495a269c9995bd5789079dc9cbd65bd23f9e
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Fri Apr 9 19:10:56 2010 -0400

    BZ580943: add more patterns to kprobe blacklist
    
    * dwflpp.cxx (build_blacklist): Add a few more entries.

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

Summary of changes:
 dwflpp.cxx                 |    2 ++
 runtime/staprun/mainloop.c |   42 ++++++++++++++++++++++++++++++++++--------
 2 files changed, 36 insertions(+), 8 deletions(-)


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


                 reply	other threads:[~2010-04-10 11:10 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=20100410111000.9226.qmail@sourceware.org \
    --to=fche@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).