mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Rabin Vincent <rabin@rab.in>
Cc: linux-kernel@vger.kernel.org
Subject: Re: function_graph selftest fails with !DYNAMIC
Date: Thu, 03 Nov 2011 12:08:27 -0400	[thread overview]
Message-ID: <1320336507.27370.18.camel@gandalf.stny.rr.com> (raw)
In-Reply-To: <20111102150255.GA6973@debian>

On Wed, 2011-11-02 at 20:32 +0530, Rabin Vincent wrote:
> The function_graph selftest fails when CONFIG_DYNAMIC_FTRACE is not set
> (tested on x86-64) on current kernels:
> 
> [    0.300124] Testing tracer function: PASSED
> [    0.446092] Testing tracer function_graph: .. no entries found ..FAILED!
> 
> Bisecting goes back to this commit:
> 
> 2b499381bc50ede01b3d8eab164ca2fad00655f0 is the first bad commit
> commit 2b499381bc50ede01b3d8eab164ca2fad00655f0

Interesting, I get the same bug at HEAD, but when I checked out this
commit, it works.

Maybe I'll kick off a bisect and see where it lands up.

Thanks,

-- Steve

> Author: Steven Rostedt <srostedt@redhat.com>
> Date:   Tue May 3 22:49:52 2011 -0400
> 
>     ftrace: Have global_ops store the functions that are to be traced
>     
>     This is a step towards each ops structure defining its own set
>     of functions to trace. As the current code with pid's and such
>     are specific to the global_ops, it is restructured to be used
>     with the global ops.
>     
>     Signed-off-by: Steven Rostedt <rostedt@goodmis.org>



  parent reply	other threads:[~2011-11-03 16:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 15:02 Rabin Vincent
2011-11-03  0:17 ` Steven Rostedt
2011-11-03 16:08 ` Steven Rostedt [this message]
2011-11-04 13:44 ` Steven Rostedt
2011-11-11 16:55   ` Rabin Vincent
2011-11-12  0:20     ` Steven Rostedt
2011-11-18 23:12 ` [tip:perf/core] ftrace: Remove force undef config value left for testing tip-bot for Steven Rostedt
2011-12-06  6:26 ` tip-bot for 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=1320336507.27370.18.camel@gandalf.stny.rr.com \
    --to=rostedt@goodmis.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rabin@rab.in \
    /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
all inboxes | Powered by JetHome®