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.3-214-g61f1a63 Date: Wed, 20 Oct 2010 17:16:00 -0000 [thread overview] Message-ID: <20101020171612.24575.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 61f1a63b261ab99923c07bf83eedcf76ae73f315 (commit) via 88637c31488f4987cc63c3f71263917dd98ca9cf (commit) via d4393459f12944f65d509b71927770080df46237 (commit) from fb72be5435594c99137073783ccdd016877a5989 (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 61f1a63b261ab99923c07bf83eedcf76ae73f315 Author: Frank Ch. Eigler <fche@elastic.org> Date: Wed Oct 20 13:13:20 2010 -0400 PR10745: automate kernel source_tree finding with stap -r /PATH/ * tapsets.cxx (init_dw): Provide diagnostics when figuring out source_tree. * session.cxx (main): Ditto. For stap -r /PATH/, heuristically infer source_tree too. commit 88637c31488f4987cc63c3f71263917dd98ca9cf Author: Frank Ch. Eigler <fche@elastic.org> Date: Wed Oct 20 11:51:34 2010 -0400 PR10745: access hidden kernel tracepoints Including xfs_types.h unconditionally on installations with no kernel debuginfo would cause normal tracepoint processing to fail too. * tapsets.cxx (tracepoint_extra_decls): Include xfs_types.h only if we know the kernel source tree. commit d4393459f12944f65d509b71927770080df46237 Author: Frank Ch. Eigler <fche@elastic.org> Date: Wed Oct 20 11:27:59 2010 -0400 PR10745: access hidden kernel tracepoints A bunch of kernel tracepoints have been declared outside the conventional include/linux/trace/* hierarchy, and left in the source tree only. By searching the source tree with some additional glob patterns, we can find them and generate debuginfo the usual way. On Fedora/RHEL, this means looking through debuginfo to find the DW_AT_comp_dir (compilation source directory), which is something like /usr/src/debug/kernels/FOO/BAR/. Nearly all tracepoints appear now accessible under RHEL6/F13 era kernels: % ls -1 /sys/kernel/debug/tracing/events/*/*/id | cut -f8 -d/ | egrep -v 'sys_(enter|exit)' | while read tp do stap -L 'kernel.trace("'$tp'")' || echo no $tp done reports no "no"s. Note that syscall tracepoints are treated specially in the kernel; stap sees only a single sys_enter / sys_exit pair, thus the egrep -v above. * session.h (kernel_source_tree): New field. * buildrun.cxx (compile_pass, make_tracequery): Add EXTRA_CFLAGS += -I.... (make_tracequery): Squish repeated TRACE_INCLUDE_PATH defines. * tapsets.cxx (tracepoint_derived_probe ctor): Relax conventions on tracepoint header file name. (tracepoint_extra_headers): Renamed to ... (tracepoint_extra_decls): New function. Include struct/type forward decls as needed. (emit_module_decls): Use new decl list style. (tracepoint_builder::init_dw): Search kernel source tree also for tracepoint headers. ----------------------------------------------------------------------- Summary of changes: buildrun.cxx | 13 +++++-- session.cxx | 21 +++++++++++ session.h | 1 + tapsets.cxx | 108 ++++++++++++++++++++++++++++++++++++++++++++++----------- 4 files changed, 118 insertions(+), 25 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2010-10-20 17:16 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=20101020171612.24575.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: 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).