linux-kernel.vger.kernel.org archive mirror
 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>,
	Thomas Gleixner <tglx@linutronix.de>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 0/2 v2] [GIT PULL][v3.2] tracing: queued updates
Date: Tue, 11 Oct 2011 11:20:26 -0400	[thread overview]
Message-ID: <20111011152026.701326733@goodmis.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1447 bytes --]


Ingo,

I found the build bug with ftrace disabled. It was in the second to last
patch of the series. It was a cut and paste error where the ftrace_is_dead()
stub had "extern static inline" which caused the error.

I rebased and pushed to my git tree. Please check the SHA1, even though
the mirrors should be updated by now.

I tested this branch with the following:

 allnoconfig + minconfig to boot

 full ftrace enabled to boot and test

 ftrace without function tracing to boot and test

 no tracing enabled to boot and test

 allmodconfig to boot and test - a call trace dumped from a non
  related bug (in slub). I will investigate this later.

 allyesconfig to build - just made sure it builds.

I'm only sending out the last two patches as the other patches are
still the same. The rebase started from the second patch.

-- Steve

Please pull the latest tip/perf/core tree, which can be found at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
tip/perf/core

Head SHA1: d696b58ca2c3ca76e784ef89a7e0453d9b7ab187


Steven Rostedt (2):
      tracing: Warn on output if the function tracer was found corrupted
      tracing: Do not allocate buffer for trace_marker

----
 kernel/trace/ftrace.c |    8 +++
 kernel/trace/trace.c  |  126 ++++++++++++++++++++++++++++++++++++++-----------
 kernel/trace/trace.h  |    2 +
 3 files changed, 108 insertions(+), 28 deletions(-)

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2011-10-11 15:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-11 15:20 Steven Rostedt [this message]
2011-10-11 15:20 ` [PATCH 1/2 v2] tracing: Warn on output if the function tracer was found corrupted Steven Rostedt
2011-10-11 15:20 ` [PATCH 2/2 v2] tracing: Do not allocate buffer for trace_marker Steven Rostedt
2011-10-12  8:16 ` [PATCH 0/2 v2] [GIT PULL][v3.2] tracing: queued updates Ingo Molnar
2011-10-12 11:21   ` Steven Rostedt
2011-10-12 13:26     ` Steven Rostedt
2011-10-12 16:23       ` Ingo Molnar
2011-10-12 16:32         ` Steven Rostedt
2011-10-13  8:59         ` Ingo Molnar
2011-10-13 13:55           ` Steven Rostedt
2011-10-13 14:00             ` 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=20111011152026.701326733@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).