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-103-gfc67feb Date: Tue, 16 Aug 2011 13:09:00 -0000 [thread overview] Message-ID: <20110816130922.5336.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 fc67febc6733e5803e6883a3757abda6268a953a (commit) from ebc08b50d71622148c9e472a3876972e3a5a59e3 (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 fc67febc6733e5803e6883a3757abda6268a953a Author: Mark Wielaard <mjw@redhat.com> Date: Tue Aug 16 14:31:29 2011 +0200 Reintroduce timer for transport cmd channel, don't wake_up unconditionally. Revert parts of commit a85c8a "runtime/io.c: Explicitly signal setting of _stp_exit_flag" and commit 46ac9e "Remove _stp_ctl_work_timer from module transport layer". Introduce a new test wake_up.exp that shows a deadlock when sending cmd messages and waking up the reader immediately. Renamed _stp_ctl_write to _stp_ctl_send, which can be called from everywhere. Rename _stp_ctl_send to _stp_ctl_send_notify that can be called from user context in the transport layer itself (this will immediately notify any readers). Document all places that use _stp_ctl_send_notify directly to clarify why that is safe. See http://sourceware.org/ml/systemtap/2011-q3/msg00163.html ----------------------------------------------------------------------- Summary of changes: runtime/io.c | 4 +- runtime/print_flush.c | 8 ++- runtime/transport/control.c | 93 ++++++++++++++++------------------- runtime/transport/control.h | 3 +- runtime/transport/transport.c | 69 +++++++++++++++++++++++-- runtime/transport/transport.h | 2 - testsuite/systemtap.base/wakeup.exp | 24 +++++++++ testsuite/systemtap.base/wakeup.stp | 13 +++++ 8 files changed, 153 insertions(+), 63 deletions(-) create mode 100644 testsuite/systemtap.base/wakeup.exp create mode 100644 testsuite/systemtap.base/wakeup.stp hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-08-16 13:09 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=20110816130922.5336.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: linkBe 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).