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-1.3-163-g994aac0 Date: Tue, 28 Sep 2010 23:27:00 -0000 [thread overview] Message-ID: <20100928232738.3472.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 994aac0e5744703fa58eb3dabcd858eca1306e10 (commit) via 37ae3931d6eff955f75319d99f507688cef054e5 (commit) via a4ab58c767f8ef1968921b5169646df1a691a02a (commit) from 448a86b7ff08eea4c2ffda8ac3249cf3cbb2e041 (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 994aac0e5744703fa58eb3dabcd858eca1306e10 Author: Josh Stone <jistone@redhat.com> Date: Tue Sep 28 14:41:37 2010 -0700 Allow de-duping in spite of STP_TIMING To enable this, we can use a Stat pointer in the same place we keep the individual pp data, so now even when the probe body is shared, separate timing data is kept. * elaborate.h (derived_probe): Add a "real" name which is unchanging, unlike the regular name that may face de-duping. * tapsets.cxx (common_probe_init): Use the "real" name for timing data. (common_probe_entryfn_prologue): Use a local stat instead of CONTEXT->statp, and initialize it from the probe data. (common_probe_entryfn_epilogue): Also use the local stat. * translate.cxx (c_unparser::emit_common_header): Remove statp, and don't use any timing anti-dupe. (c_unparser::emit_module_init): Timing globals are now based on the "real" probe names. (c_unparser::emit_module_exit): Ditto. (c_unparser::emit_probe): No more timing anti-dupe. (translate_pass): Declare the new global timing struct, and point to it accordingly in STAP_PROBE_INIT. commit 37ae3931d6eff955f75319d99f507688cef054e5 Author: Josh Stone <jistone@redhat.com> Date: Fri Sep 24 15:16:36 2010 -0700 Simplify the '?' removal for STP_TIMING Add a new flag to probe_point::print() so the extra details can be avoided. This skips '?', '!', and any conditionals as well. * staptree.cxx (probe_point::print): Make the extras optional. (probe_point::str): Pass along the choice of extras. * translate.cxx (c_unparser::emit_module_exit): Let the print routine skip the extra flags, rather than trying to strip them out manually. commit a4ab58c767f8ef1968921b5169646df1a691a02a Author: Josh Stone <jistone@redhat.com> Date: Fri Sep 24 14:54:54 2010 -0700 STP_TIMING indent/whitespace cleanup ----------------------------------------------------------------------- Summary of changes: elaborate.cxx | 4 +- elaborate.h | 1 + staptree.cxx | 8 ++- staptree.h | 4 +- tapsets.cxx | 12 +++-- translate.cxx | 122 +++++++++++++++++++++++++++----------------------------- 6 files changed, 76 insertions(+), 75 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-09-28 23:27 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=20100928232738.3472.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: 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).