public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: serhei@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.8-243-ge0f2efe Date: Wed, 19 Sep 2012 15:06:00 -0000 [thread overview] Message-ID: <20120919150648.980.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 e0f2efecc13e87ef3b8f20f890401d29f5ef744d (commit) from 731a5359e2f226a0a7fa253265cf59d06c4356bf (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 e0f2efecc13e87ef3b8f20f890401d29f5ef744d Author: Serguei Makarov <smakarov@redhat.com> Date: Wed Sep 19 11:00:22 2012 -0400 PR6580 clarification: comment explaining suitability of current kluge for _stp_get_uregs() clearing kernel cache. The inefficiency alluded to only occurs when interspersing *partial* kernel and user unwinds, e.g. try this with -DDEBUG_UNWIND=1: stack(0); ustack(0); stack(1); ustack(1); ... ----------------------------------------------------------------------- Summary of changes: runtime/stack.c | 23 +++++++++++++++++------ 1 files changed, 17 insertions(+), 6 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-09-19 15:06 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=20120919150648.980.qmail@sourceware.org \ --to=serhei@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).