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-83-g5738a98 Date: Thu, 11 Aug 2011 11:24:00 -0000 [thread overview] Message-ID: <20110811112447.14845.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 5738a9825160b4fdc76882d30578c4ae06c058f5 (commit) via 4310ef773dfeba9dde69f905c8718897894ca4ff (commit) from b7edd3387dc69932174e8bb65b08f94a9045ae50 (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 5738a9825160b4fdc76882d30578c4ae06c058f5 Author: Mark Wielaard <mjw@redhat.com> Date: Thu Aug 11 12:34:01 2011 +0200 Only collect and emit unwind data in translator if the session needs it. When we hit the translator the session already knows whether or not it will possibly need the unwind data. Only collect and emit it, if the session does. This can save writing out tens of MB to stap-symbols.h for simple scripts that never call any backtrace() function. commit 4310ef773dfeba9dde69f905c8718897894ca4ff Author: Mark Wielaard <mjw@redhat.com> Date: Thu Aug 11 12:03:55 2011 +0200 Remove preempt_disable from unwind hotpath. We only need to preempt_disable when we fail to find a kernel module to unwind through so we can call __module_text_address. ----------------------------------------------------------------------- Summary of changes: runtime/unwind.c | 7 ++++--- translate.cxx | 13 ++++++++----- 2 files changed, 12 insertions(+), 8 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-08-11 11:24 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=20110811112447.14845.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).