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/5] ftrace: updates for tip
Date: Wed, 3 Dec 2008 09:11:18 +0100	[thread overview]
Message-ID: <20081203081118.GD21006@elte.hu> (raw)
In-Reply-To: <20081203045001.367443457@goodmis.org>


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

> Ingo,
> 
> Most of thes patches are improvements to function graph. I'm
> working on making a way to pick a function to trace, which the
> patch function entry patch is needed.
> 
> The one ring buffer patch converts all variables called 'page' to
> 'bpage' as per Andrew's request.
> 
> The following patches are in:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> 
>     branch: tip/devel
> 
> 
> Steven Rostedt (5):
>       ftrace: add ftrace_graph_stop
>       ring-buffer: change page variables to bpage
>       ftrace: print real return in dumpstack for function graph
>       ftrace: function graph return for function entry
>       ftrace: add checks on ret stack in function graph
> 
> ----
>  arch/x86/kernel/dumpstack.c    |   34 ++++++++++-
>  arch/x86/kernel/dumpstack.h    |    2 +-
>  arch/x86/kernel/dumpstack_32.c |    5 +-
>  arch/x86/kernel/dumpstack_64.c |    7 +-
>  arch/x86/kernel/entry_32.S     |    3 +
>  arch/x86/kernel/entry_64.S     |    3 +
>  arch/x86/kernel/ftrace.c       |   34 +++++++++--
>  include/linux/ftrace.h         |    4 +-
>  kernel/trace/ftrace.c          |   15 ++++-
>  kernel/trace/ring_buffer.c     |  130 ++++++++++++++++++++--------------------
>  kernel/trace/trace.c           |    4 +-
>  kernel/trace/trace.h           |    2 +-
>  12 files changed, 161 insertions(+), 82 deletions(-)

pulled into tip/tracing/ftrace, thanks Steve!

	Ingo

  parent reply	other threads:[~2008-12-03  8:11 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03  4:50 [PATCH 0/5] ftrace: updates for tip Steven Rostedt
2008-12-03  4:50 ` [PATCH 1/5] ftrace: add ftrace_graph_stop Steven Rostedt
2008-12-03  4:50 ` [PATCH 2/5] ring-buffer: change page variables to bpage Steven Rostedt
2008-12-03  4:50 ` [PATCH 3/5] ftrace: print real return in dumpstack for function graph Steven Rostedt
2008-12-03  8:11   ` Ingo Molnar
2008-12-03 11:44     ` Steven Rostedt
2008-12-03  4:50 ` [PATCH 4/5] ftrace: function graph return for function entry Steven Rostedt
2008-12-03  8:13   ` Ingo Molnar
2008-12-03 10:05     ` Ingo Molnar
2008-12-03 11:59       ` Steven Rostedt
2008-12-03 13:23         ` Frédéric Weisbecker
2008-12-03 14:04           ` Steven Rostedt
2008-12-03 11:49     ` Steven Rostedt
2008-12-03 13:19       ` Frédéric Weisbecker
2008-12-03  4:50 ` [PATCH 5/5] ftrace: add checks on ret stack in function graph Steven Rostedt
2008-12-03  8:11 ` Ingo Molnar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-01-21 23:53 [PATCH 0/5] ftrace: updates for tip Steven Rostedt
2009-01-22  9:32 ` Ingo Molnar
2008-12-02 20:34 [PATCH 0/5] ftrace " Steven Rostedt
2008-12-03  7:57 ` 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=20081203081118.GD21006@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