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.6-384-gd7a438e
Date: Sun, 06 Nov 2011 22:02:00 -0000 [thread overview]
Message-ID: <20111106220202.17502.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 d7a438e53bc6140f4d4a6883515c87054721135b (commit)
via cd125e94b239eec3c69726f7c3647354362c637a (commit)
from 61019d8d61f25c17792d134ce3d01289e183bbfa (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 d7a438e53bc6140f4d4a6883515c87054721135b
Author: Frank Ch. Eigler <fche@redhat.com>
Date: Sun Nov 6 16:55:59 2011 -0500
PR13193: pessimize dynamic-module test case
This variant of the test case serializes the module coming/going
traffic, to work around what are assumed to be kernel kprobes
problems. With &'s wherever ;'s are, even manly, glutamine-fortified
bicept-curling kernels quiver with fear.
commit cd125e94b239eec3c69726f7c3647354362c637a
Author: Frank Ch. Eigler <fche@redhat.com>
Date: Sun Nov 6 13:44:50 2011 -0500
PR13193: disable kprobes-optimization at staprun startup time
* runtime/staprun/staprun.c (disable_kprobes_optimization): New function,
called from ...
(init_staprun): ... here, unless getenv("STAP_PR13193_OVERRIDE").
-----------------------------------------------------------------------
Summary of changes:
runtime/staprun/staprun.c | 41 +++++++++++++++++++++++++++++++++++
testsuite/systemtap.base/bz6503.exp | 2 +-
2 files changed, 42 insertions(+), 1 deletions(-)
hooks/post-receive
--
systemtap: system-wide probe/trace tool
reply other threads:[~2011-11-06 22: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=20111106220202.17502.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).