public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: dsmith@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.8-125-g0e0e60b Date: Thu, 02 Aug 2012 15:01:00 -0000 [thread overview] Message-ID: <20120802150144.14684.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 0e0e60b276f6a839b56d302e31432adaa0f02440 (commit) from 9d2b21df1694ef312a2312a3fd6e7d046dcdf672 (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 0e0e60b276f6a839b56d302e31432adaa0f02440 Author: David Smith <dsmith@redhat.com> Date: Thu Aug 2 10:01:23 2012 -0500 Fixed PR14427 by handling old and new task_work interface. * runtime/linux/autoconf-utrace-via-tracepoints.c: Just includes task_work.h to determine existence of task_work feature. * runtime/linux/autoconf-task_work-struct.c: New file. * buildrun.cxx (compile_pass): Add autoconf-task_work-struct test. * runtime/linux/task_work_compatibility.h: New header that mask differences between old task_work interface and new one. * runtime/linux/task_finder2.c: Handle removal of 'data' parameter from task_work struct by embedding stap_task_finder_target in __stp_tf_task_work structure. * runtime/stp_task_work.c: Include task_work_compatibility.h instead of task_work.h. * runtime/stp_utrace.c (utrace_task_alloc): Update init_task_work() function call to compatibility function call. ----------------------------------------------------------------------- Summary of changes: buildrun.cxx | 1 + runtime/linux/autoconf-task_work-struct.c | 10 +++++ runtime/linux/autoconf-utrace-via-tracepoints.c | 11 +---- runtime/linux/task_finder2.c | 21 +++++++--- runtime/linux/task_work_compatibility.h | 46 +++++++++++++++++++++++ runtime/stp_task_work.c | 2 +- runtime/stp_utrace.c | 2 +- 7 files changed, 75 insertions(+), 18 deletions(-) create mode 100644 runtime/linux/autoconf-task_work-struct.c create mode 100644 runtime/linux/task_work_compatibility.h hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-08-02 15:01 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=20120802150144.14684.qmail@sourceware.org \ --to=dsmith@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).