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-247-ge357582 Date: Fri, 21 Sep 2012 20:15:00 -0000 [thread overview] Message-ID: <20120921201459.10216.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 e3575828e07be265fd6628a2c58103bf2fdf7535 (commit) from 5c3e49ce97d57cc97e2412e9fb7a03e6d0093ad0 (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 e3575828e07be265fd6628a2c58103bf2fdf7535 Author: David Smith <dsmith@redhat.com> Date: Fri Sep 21 15:13:28 2012 -0500 (PR14571 partial fix) For dyninst, use TLS for map and stat data. * runtime/dyninst/tls_data.c: New file. * runtime/stat.c (struct _Stat): Add a tls_data_container_t structure. (_stp_stat_tls_object_init): New function. (_stp_stat_tls_object_free): Ditto. (_stp_stat_init): Instead of directly allocating percpu data, for dyninst set up tls data to be created when accessed by calling _stp_tls_data_container_init(). (_stp_stat_del): For dyninst, call _stp_tls_data_container_cleanup() to remove all the tls data. (_stp_stat_add): For dyninst, get the proper tls stat object. (_stp_stat_get_cpu): Deleted unused function. (_stp_stat_get): For dyninst, get the proper tls stat objects. (_stp_stat_clear): For dyninst, clear the stat in each thread's tls data. * runtime/stat.h (struct stat_data): Add a tls_data_object_t structure. * runtime/map.c (_stp_map_tls_object_init): New function. (_stp_map_tls_object_free): Ditto. (_stp_pmap_new): Instead of directly allocating percpu data, for dyninst set up tls data to be created when accessed by calling _stp_tls_data_container_init(). (_stp_pmap_clear): For dyninst, clear the map in each thread's tls data. (_stp_pmap_del): For dyninst, call _stp_tls_data_container_cleanup() to remove all the tls data. (_stp_pmap_agg): Add dyninst support. * runtime/map.h (struct map_root): Add a tls_data_object_t structure. (struct pmap): Add a tls_data_container_t structure. * runtime/map-stat.c (_stp_hstat_tls_object_init): New function. (_stp_pmap_new_hstat_linear): For dyninst, override the standard tls data object init function with _stp_hstat_tls_object_init(), which knows how to handle hstats. (_stp_pmap_new_hstat_log): Ditto. * runtime/pmap-gen.c (_stp_pmap_tls_object_init): New function. (_stp_pmap_new): For dyninst, override the standard tls data object init function with _stp_pmap_tls_object_init(), which knows how to handle pmaps. (_stp_pmap_set): For dyninst, get the proper tls pmap object. (_stp_pmap_add): Ditto. (_stp_pmap_get_cpu): Ditto. (_stp_pmap_get): Ditto. (_stp_pmap_del): Ditto. * runtime/dyninst/linux_defs.h: Added container_of(), list_entry(), list_for_each_entry(), and list_for_each_entry_safe(). ----------------------------------------------------------------------- Summary of changes: runtime/dyninst/linux_defs.h | 19 +++++ runtime/dyninst/tls_data.c | 178 ++++++++++++++++++++++++++++++++++++++++++ runtime/map-stat.c | 42 ++++++++++- runtime/map.c | 145 ++++++++++++++++++++++++++++++---- runtime/map.h | 18 ++++- runtime/pmap-gen.c | 82 +++++++++++++++++++- runtime/stat.c | 124 ++++++++++++++++++++++++----- runtime/stat.h | 15 ++++- 8 files changed, 580 insertions(+), 43 deletions(-) create mode 100644 runtime/dyninst/tls_data.c hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-09-21 20:15 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=20120921201459.10216.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).