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/8] ftrace: updates to tip
Date: Tue, 20 Jan 2009 13:05:12 +0100	[thread overview]
Message-ID: <20090120120512.GA7790@elte.hu> (raw)
In-Reply-To: <20090120001542.687427797@goodmis.org>


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

> Ingo,
> 
> The one patch I did here, will need to go to stable as well. I'll write
> up a patch against stable, and as soon as it gets into Linus's tree,
> it should also be pulled into stable as well. Without the patch, some
> archs will not be able to perform any tracing. There is an alignment
> issue that will cause the ring buffer to fail to commit any transactions.
> 
> -- Steve
> 
> 
> The following patches are in:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
> 
>     branch: tip/devel
> 
> 
> Lai Jiangshan (1):
>       trace_workqueue: use percpu data for workqueue stat
> 
> Markus Metzger (6):
>       x86, ftrace, hw-branch-tracer: support hotplug cpus
>       x86, ftrace, hw-branch-tracer: dump trace on oops
>       x86, ftrace, hw-branch-tracer: reset trace buffer on close
>       x86, ftrace, hw-branch-tracer: change trace format
>       x86, ftrace, hw-branch-tracer: documentation
>       x86, ds, bts: cleanup DS configuration
> 
> Steven Rostedt (1):
>       ring-buffer: fix alignment problem
> 
> ----
>  Documentation/ftrace.txt         |   74 ++++++++++++++++
>  arch/x86/kernel/ds.c             |   31 ++++---
>  arch/x86/kernel/dumpstack.c      |    6 ++
>  include/linux/ftrace.h           |   13 +++
>  kernel/trace/ring_buffer.c       |    2 +-
>  kernel/trace/trace.h             |    1 -
>  kernel/trace/trace_hw_branches.c |  173 +++++++++++++++++++++++++++++++-------
>  kernel/trace/trace_workqueue.c   |   64 +++++++--------
>  8 files changed, 281 insertions(+), 83 deletions(-)

Pulled into tip/tracing/ftrace, thanks Steve!

	Ingo

      parent reply	other threads:[~2009-01-20 12:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-20  0:15 [PATCH 0/8] ftrace: updates to tip Steven Rostedt
2009-01-20  0:15 ` [PATCH 1/8] x86, ftrace, hw-branch-tracer: support hotplug cpus Steven Rostedt
2009-01-20  0:15 ` [PATCH 2/8] x86, ftrace, hw-branch-tracer: dump trace on oops Steven Rostedt
2009-01-20  0:15 ` [PATCH 3/8] x86, ftrace, hw-branch-tracer: reset trace buffer on close Steven Rostedt
2009-01-20  0:15 ` [PATCH 4/8] x86, ftrace, hw-branch-tracer: change trace format Steven Rostedt
2009-01-20  0:15 ` [PATCH 5/8] x86, ftrace, hw-branch-tracer: documentation Steven Rostedt
2009-01-20  0:15 ` [PATCH 6/8] x86, ds, bts: cleanup DS configuration Steven Rostedt
2009-01-20  0:15 ` [PATCH 7/8] ring-buffer: fix alignment problem Steven Rostedt
2009-01-20  0:15 ` [PATCH 8/8] trace_workqueue: use percpu data for workqueue stat Steven Rostedt
2009-01-20  0:41 ` [PATCH 0/8] ftrace: updates to tip Steven Rostedt
2009-01-20  0:42   ` Steven Rostedt
2009-01-20 12:05 ` Ingo Molnar [this message]

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=20090120120512.GA7790@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.