public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Subject: [PATCH v2 0/7] ftrace: updates for tip
Date: Fri, 06 Feb 2009 10:21:51 -0500	[thread overview]
Message-ID: <20090206152151.962749733@goodmis.org> (raw)

Ingo,

This is still based off of tip/master since it is not all focused
on ftrace (has NMI generic code). I'll let you cherry pick and
figure out what goes where.

I tried to cherry pick them into tracing/ftrace and hit a bit of conflicts.
Next time, I'll just develop against tip/tracing/ftrace or
tip/tracing/core.

Changes since the first version:

 - Added Mathieu Desnoyers credit in the in_nmi change log.

 - Included the original ring buffer changes which these are
   based on and that I do not see in tip/master.

 - Added a comment fix patch by Wenji.

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 (6):
      ring-buffer: add NMI protection for spinlocks
      ring-buffer: allow tracing_off to be used in core kernel code
      ftrace, x86: rename in_nmi variable
      nmi: add generic nmi tracking state
      ftrace: change function graph tracer to use new in_nmi
      ring-buffer: use generic version of in_nmi

Wenji Huang (1):
      trace: trivial fixes in comment typos.

----
 arch/x86/Kconfig            |    1 +
 arch/x86/kernel/ftrace.c    |   35 ++++++++---------------------------
 include/linux/ftrace.h      |    2 +-
 include/linux/ftrace_irq.h  |    2 +-
 include/linux/hardirq.h     |   15 +++++++++++++++
 include/linux/ring_buffer.h |    9 +++++++++
 kernel/trace/Kconfig        |    8 ++++++++
 kernel/trace/ftrace.c       |    6 +++---
 kernel/trace/ring_buffer.c  |   31 +++++++++++++++++++++++++++++--
 kernel/trace/trace.h        |    6 +++---
 10 files changed, 78 insertions(+), 37 deletions(-)
-- 

             reply	other threads:[~2009-02-06 15:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-06 15:21 Steven Rostedt [this message]
2009-02-06 15:21 ` [PATCH v2 1/7] ring-buffer: add NMI protection for spinlocks Steven Rostedt
2009-02-06 19:40   ` Mathieu Desnoyers
2009-02-06 19:49     ` Steven Rostedt
2009-02-06 15:21 ` [PATCH v2 2/7] ring-buffer: allow tracing_off to be used in core kernel code Steven Rostedt
2009-02-06 15:21 ` [PATCH v2 3/7] ftrace, x86: rename in_nmi variable Steven Rostedt
2009-02-06 15:21 ` [PATCH v2 4/7] nmi: add generic nmi tracking state Steven Rostedt
2009-02-06 15:21 ` [PATCH v2 5/7] ftrace: change function graph tracer to use new in_nmi Steven Rostedt
2009-02-06 15:21 ` [PATCH v2 6/7] ring-buffer: use generic version of in_nmi Steven Rostedt
2009-02-06 15:21 ` [PATCH v2 7/7] trace: trivial fixes in comment typos Steven Rostedt

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=20090206152151.962749733@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.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