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.3-398-g0c655dc
Date: Thu, 16 Dec 2010 20:55:00 -0000	[thread overview]
Message-ID: <20101216205553.13821.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  0c655dc0639385469318047d7c96b75ae50fa924 (commit)
      from  04c0405d83180b27a1a96e2f051da4e9e0707e03 (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 0c655dc0639385469318047d7c96b75ae50fa924
Author: David Smith <dsmith@redhat.com>
Date:   Thu Dec 16 14:55:25 2010 -0600

    Fix PR11388 by handling syscall.mmap changes for 2.6.33+ kernels.
    
    * tapset/syscalls.stp: Use arch-generic sys_mmap_pgoff() for syscall.mmap2
      if kernel version is 2.6.33 or higher.
    * tapset/i386/syscalls.stp: Only use arch-specific syscall.mmap* probes if
      kernel version is less than 2.6.33.
    * tapset/ia64/syscalls.stp: Ditto.
    * tapset/powerpc/syscalls.stp: Ditto.
    * tapset/s390/syscalls.stp: Ditto.
    * tapset/x86_64/syscalls.stp: Ditto.  Also move sys_mmap_pgoff() probe to
      syscall.mmap2 alias (instead of syscall.mmap alias).
    * testsuite/buildok/syscalls-detailed.stp: Add generic syscall.mmap2 test
      if kernel version is 2.6.33 or higher.
    * testsuite/buildok/syscalls-arch-detailed.stp: Only test arch-specific
      syscall.mmap* probes if kernel version is less than 2.6.33.

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

Summary of changes:
 tapset/i386/syscalls.stp                     |    5 ++++
 tapset/ia64/syscalls.stp                     |    5 ++++
 tapset/powerpc/syscalls.stp                  |    5 ++++
 tapset/s390/syscalls.stp                     |    5 ++++
 tapset/syscalls.stp                          |   29 ++++++++++++++++++++++++++
 tapset/x86_64/syscalls.stp                   |   21 +++++++++++-------
 testsuite/buildok/syscalls-arch-detailed.stp |    6 +++++
 testsuite/buildok/syscalls-detailed.stp      |   14 ++++++++++++
 8 files changed, 82 insertions(+), 8 deletions(-)


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


                 reply	other threads:[~2010-12-16 20:55 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=20101216205553.13821.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: 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).