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.2-238-gc8bc204 Date: Thu, 10 Jun 2010 02:18:00 -0000 [thread overview] Message-ID: <20100610021825.26188.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 c8bc20447d3c55a6d5b58b32275559fff5dbccfb (commit) via 6bff37abacf95b60a1d8d4c83c9e59e42ae1a7b9 (commit) via 18a4c1b66409e612192bc4188f3f91bbad97d79e (commit) via 71f083934a8aeb52a9cc331a00e39453cf412774 (commit) via ca43a52c51367b1c2f582b31c3f3515495eb3b0a (commit) from 8b5c229525fd493416a34a7877f96ea2615953d4 (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 c8bc20447d3c55a6d5b58b32275559fff5dbccfb Author: Josh Stone <jistone@redhat.com> Date: Wed Jun 9 21:48:51 2010 -0400 Give non-x86 a chance at uprobes SDT * tapsets.cxx (sdt_uprobe_var_expanding_visitor): No need to assert that we know dwarf_regs unless we actually encountered STAP_SDT_V2 with arg_count > 0. V1 should continue to work on other architectures. commit 6bff37abacf95b60a1d8d4c83c9e59e42ae1a7b9 Author: Josh Stone <jistone@redhat.com> Date: Wed Jun 9 21:44:42 2010 -0400 Let probe_bench work on archs besides x86_64 The cycles code is too x86_64-centric, but for now at least it's been neutered to let other archs report basic timing numbers. * scripts/probe_bench/bench.stp: Use get_cycles() instead of rdtsc(). * scripts/probe_bench/bench.c (rdtsc): Return 0 unless on x86_64. This needs more work and inline assembly to fit more architectures. commit 18a4c1b66409e612192bc4188f3f91bbad97d79e Author: Josh Stone <jistone@redhat.com> Date: Wed Jun 9 21:44:11 2010 -0400 Ignore probe_bench's generated files commit 71f083934a8aeb52a9cc331a00e39453cf412774 Author: Josh Stone <jistone@redhat.com> Date: Wed Jun 9 21:41:06 2010 -0400 Short out errors in probe_bench * scripts/probe_bench/bench.sh (setup_test, stap_test): Report when an error occurred and return. commit ca43a52c51367b1c2f582b31c3f3515495eb3b0a Author: Josh Stone <jistone@redhat.com> Date: Wed Jun 9 21:38:56 2010 -0400 Make sure the probe_bench can find sdt.h * scripts/probe_bench/bench.sh (setup_test): Give -I$STAP/include to gcc. ----------------------------------------------------------------------- Summary of changes: scripts/probe_perf/.gitignore | 3 ++ scripts/probe_perf/bench.c | 11 ++++++++- scripts/probe_perf/bench.sh | 4 ++- scripts/probe_perf/bench.stp | 42 +++++++++++++++++----------------------- tapsets.cxx | 2 +- 5 files changed, 34 insertions(+), 28 deletions(-) create mode 100644 scripts/probe_perf/.gitignore hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-06-10 2:18 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=20100610021825.26188.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).