All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH 0/7] [GIT PULL] tracing: updates
Date: Fri, 2 Apr 2010 18:39:46 +0200	[thread overview]
Message-ID: <20100402163946.GC20963@elte.hu> (raw)
In-Reply-To: <20100401031735.683626160@goodmis.org>


* Steven Rostedt <rostedt@goodmis.org> wrote:

> Ingo,
> 
> Please pull the latest tip/tracing/core tree, which can be found at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> tip/tracing/core
> 
> 
> Li Zefan (3):
>       tracing: Convert some signal events to DEFINE_TRACE
>       tracing: Update comments
>       tracing: Remove side effect from module tracepoints that caused a GPF
> 
> Steven Rostedt (4):
>       tracing: Fix compile error in module tracepoints when MODULE_UNLOAD not set
>       ring-buffer: Add place holder recording of dropped events
>       tracing: Show the lost events in the trace_pipe output
>       ring-buffer: Add lost event count to end of sub buffer
> 
> ----
>  drivers/oprofile/cpu_buffer.c        |    4 +-
>  include/linux/ftrace_event.h         |    1 +
>  include/linux/module.h               |    6 +-
>  include/linux/ring_buffer.h          |    6 +-
>  include/trace/events/module.h        |   18 ++++--
>  include/trace/events/signal.h        |   52 +++++++----------
>  include/trace/ftrace.h               |   33 ++++++-----
>  kernel/module.c                      |    8 +-
>  kernel/trace/ring_buffer.c           |  101 ++++++++++++++++++++++++++++++++--
>  kernel/trace/ring_buffer_benchmark.c |    2 +-
>  kernel/trace/trace.c                 |   30 +++++++---
>  kernel/trace/trace_functions_graph.c |    5 +-
>  kernel/trace/trace_selftest.c        |    2 +-
>  13 files changed, 187 insertions(+), 81 deletions(-)

Pulled, thanks a lot Steve!

	Ingo

  parent reply	other threads:[~2010-04-02 16:40 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-01  3:17 [PATCH 0/7] [GIT PULL] tracing: updates Steven Rostedt
2010-04-01  3:17 ` [PATCH 1/7] tracing: Convert some signal events to DEFINE_TRACE Steven Rostedt
2010-04-01  3:17 ` [PATCH 2/7] tracing: Update comments Steven Rostedt
2010-04-01  3:17 ` [PATCH 3/7] tracing: Remove side effect from module tracepoints that caused a GPF Steven Rostedt
2010-04-01  3:17 ` [PATCH 4/7] tracing: Fix compile error in module tracepoints when MODULE_UNLOAD not set Steven Rostedt
2010-04-01  3:17 ` [PATCH 5/7] ring-buffer: Add place holder recording of dropped events Steven Rostedt
2010-04-01  3:17 ` [PATCH 6/7] tracing: Show the lost events in the trace_pipe output Steven Rostedt
2010-04-01  3:17 ` [PATCH 7/7] ring-buffer: Add lost event count to end of sub buffer Steven Rostedt
2010-04-01  6:13   ` Frederic Weisbecker
2010-04-01 12:23     ` Steven Rostedt
2010-04-08 23:42       ` Frederic Weisbecker
2010-04-02 16:39 ` Ingo Molnar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-07-22 20:24 [PATCH 0/7] [GIT PULL] tracing: updates Steven Rostedt
2010-07-23  7:12 ` Ingo Molnar
2010-02-25 19:43 [PATCH 0/7][GIT " Steven Rostedt
2010-02-26  8:21 ` Ingo Molnar

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=20100402163946.GC20963@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.