public inbox for linux-kernel@vger.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/8] [GIT PULL] tracing: various updates
Date: Fri, 30 Apr 2010 10:00:55 +0200	[thread overview]
Message-ID: <20100430080055.GC20342@elte.hu> (raw)
In-Reply-To: <20100428012723.119106602@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
> 
> 
> Chase Douglas (2):
>       tracing: Add documentation for trace commands mod, traceon/traceoff
>       tracing: Show sample std dev in function profiling
> 
> David Miller (1):
>       ring-buffer: Make non-consuming read less expensive with lots of cpus.
> 
> Jiri Olsa (3):
>       tracing: Add ftrace events for graph tracer
>       tracing: Have graph flags passed in to ouput functions
>       tracing: Add graph output support for irqsoff tracer
> 
> Steven Rostedt (2):
>       ring-buffer: Make benchmark handle missed events
>       tracing: Fix sleep time function profiling
> 
> ----
>  Documentation/trace/ftrace.txt       |   44 ++++++
>  include/linux/ftrace.h               |   15 ++-
>  include/linux/ring_buffer.h          |    4 +-
>  kernel/trace/ftrace.c                |   30 ++++-
>  kernel/trace/ring_buffer.c           |   64 +++++++--
>  kernel/trace/ring_buffer_benchmark.c |    3 +-
>  kernel/trace/trace.c                 |   46 ++++--
>  kernel/trace/trace.h                 |   27 +++-
>  kernel/trace/trace_functions_graph.c |  164 +++++++++++++--------
>  kernel/trace/trace_irqsoff.c         |  271 ++++++++++++++++++++++++++++++++--
>  10 files changed, 560 insertions(+), 108 deletions(-)

Pulled, thanks a lot Steve!

	Ingo

  parent reply	other threads:[~2010-04-30 18:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28  1:27 [PATCH 0/8] [GIT PULL] tracing: various updates Steven Rostedt
2010-04-28  1:27 ` [PATCH 1/8] tracing: Add ftrace events for graph tracer Steven Rostedt
2010-04-28  1:27 ` [PATCH 2/8] tracing: Have graph flags passed in to ouput functions Steven Rostedt
2010-04-28  1:27 ` [PATCH 3/8] tracing: Add graph output support for irqsoff tracer Steven Rostedt
2010-04-28  1:27 ` [PATCH 4/8] ring-buffer: Make non-consuming read less expensive with lots of cpus Steven Rostedt
2010-04-28  1:27 ` [PATCH 5/8] ring-buffer: Make benchmark handle missed events Steven Rostedt
2010-04-28  1:27 ` [PATCH 6/8] tracing: Add documentation for trace commands mod, traceon/traceoff Steven Rostedt
2010-04-28  1:27 ` [PATCH 7/8] tracing: Show sample std dev in function profiling Steven Rostedt
2010-04-28  1:27 ` [PATCH 8/8] tracing: Fix sleep time " Steven Rostedt
2010-04-30  8:00 ` Ingo Molnar [this message]
2010-04-30  9:47   ` [PATCH 0/8] [GIT PULL] tracing: various updates 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=20100430080055.GC20342@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox