public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: cmeek@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.8-194-gb34058d
Date: Wed, 15 Aug 2012 19:48:00 -0000	[thread overview]
Message-ID: <20120815194847.5541.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  b34058d5462990f7c58fd70716610430de1756e7 (commit)
      from  7b4a162064d74b0fd082065e808485776ec9a0c5 (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 b34058d5462990f7c58fd70716610430de1756e7
Author: Chris Meek <cmeek@redhat.com>
Date:   Wed Aug 15 15:44:55 2012 -0400

    PR11659: Hook into the panic_notifier_list
    
    This feature lets stap dump the trace buffers to the serial console on a
    kernel panic. The basic functionality is there, but it could use some
    tweeking including adding a summary report at the end of the dump.
    Currently it only works for the relay buffer V2.

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

Summary of changes:
 runtime/transport/symbols.c   |   93 ++++++++++++++++++++++++++++++++++++++++-
 runtime/transport/transport.c |   19 ++++++++
 2 files changed, 111 insertions(+), 1 deletions(-)


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


                 reply	other threads:[~2012-08-15 19:48 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=20120815194847.5541.qmail@sourceware.org \
    --to=cmeek@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).