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.0-315-g4a0ae64
Date: Wed, 02 Dec 2009 21:17:00 -0000	[thread overview]
Message-ID: <20091202211729.11223.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  4a0ae64c47b159d4dd0ea471f1f8044503843a7f (commit)
      from  c10fce7d6aaa57a4f94f9d7aeea906597456f7ce (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 4a0ae64c47b159d4dd0ea471f1f8044503843a7f
Author: David Smith <dsmith@redhat.com>
Date:   Wed Dec 2 15:16:10 2009 -0600

    Fix PR 11034 by directly allocating per-cpu context data.
    * translate.cxx (emit_common_header): Change type of 'contexts' to an
      array of struct context pointers.
      (emit_module_init): Allocate a context structure for each possible cpu.
      Free each if an error occurs.
      (emit_module_exit): Update contexts reference.  Free each possible cpu's
      context structure.
    * tapsets.cxx (common_probe_entryfn_prologue): Use array instead of percpu
      data for context structure.

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

Summary of changes:
 tapsets.cxx   |    2 +-
 translate.cxx |   36 ++++++++++++++++++++++++++++--------
 2 files changed, 29 insertions(+), 9 deletions(-)


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


                 reply	other threads:[~2009-12-02 21:17 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=20091202211729.11223.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).