public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: mark@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-227-g967ec1f
Date: Mon, 19 Sep 2011 13:56:00 -0000	[thread overview]
Message-ID: <20110919135612.32353.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  967ec1f55256eb2d601ce0be5916bb46085f36db (commit)
      from  52dd8bd8b27650431f3362312411891fde7b3c58 (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 967ec1f55256eb2d601ce0be5916bb46085f36db
Author: Mark Wielaard <mjw@redhat.com>
Date:   Mon Sep 19 15:42:19 2011 +0200

    Remove arch specific _stp_probing_32bit_app() and _stp_get_regparm().
    
    Both functions were doing more than necessary and didn't actually need
    access to the current regs. _STP_PROBE_STATE_USER_MODE tells us whether
    the current probe triggered in user mode. _stp_is_compat_task() tells
    us whether the current task is a 32-on-64 process.
    
    * runtime/compatdefs.h (_stp_is_compat_task): Defined also when CONFIG_COMPAT
      is undefined (to always return false).
    * runtime/loc2c-runtime.h: u_fetch_register() and u_store_register() are
      only called from user space dwarf context. Only needs _stp_is_compat_task()
      test.
    * runtime/regs.c: Remove arch specific _stp_probing_32bit_app() and
      _stp_get_regparm() functions.
    * tapset/i386/registers.stp (_stp_arg): Check regparm directly.
    * tapset/powerpc/registers.stp (probing_32bit_app): Use _stp_is_compat_task()
      test.
    * tapset/s390/registers.stp (probing_32bit_app): Likewise.
    * tapset/x86_64/registers.stp (_stp_arg): Check regparm directly.
      (probing_32bit_app): Use _stp_is_compat_task() test.
      (regparm): Likewise.

-----------------------------------------------------------------------

Summary of changes:
 runtime/compatdefs.h         |    7 +++++++
 runtime/loc2c-runtime.h      |    4 ++--
 runtime/regs.c               |   37 -------------------------------------
 tapset/i386/registers.stp    |    9 ++++++++-
 tapset/powerpc/registers.stp |    2 +-
 tapset/s390/registers.stp    |    5 ++---
 tapset/x86_64/registers.stp  |   18 +++++++++++++-----
 7 files changed, 33 insertions(+), 49 deletions(-)


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2011-09-19 13:56 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=20110919135612.32353.qmail@sourceware.org \
    --to=mark@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: link
Be 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).