mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	linux-kernel@vger.kernel.org,
	Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: ftrace: preemptoff selftest not working
Date: Tue, 18 Nov 2008 18:06:35 +0100	[thread overview]
Message-ID: <20081118170635.GB4417@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20081118144751.GA30358@elte.hu>

On Tue, Nov 18, 2008 at 03:47:51PM +0100, Ingo Molnar wrote:
> 
> * Steven Rostedt <rostedt@goodmis.org> wrote:
> 
> > 
> > On Tue, 18 Nov 2008, Ingo Molnar wrote:
> > > 
> > > * Steven Rostedt <rostedt@goodmis.org> wrote:
> > > 
> > > > > Hence the trace buffer will be empty. The patch below makes the 
> > > > > selftests working for me, since then they run in preemptible 
> > > > > context. But it is ugly and I'm not proposing it for upstream ;)
> > > > > 
> > > > > Just wanted to make you aware that there is a bug.
> > > > 
> > > > Yep, this might be a better answer than what I put into linux-tip 
> > > > (and my git repo).
> > > > 
> > > > See:
> > > > 
> > > >   ftrace: force pass of preemptoff selftest
> > > > 
> > > > The cause of the bug was the conversion of the BKL back to a 
> > > > spinlock, and making it non preempt.  The initcall code is called 
> > > > with the BKL applied which now means it can not preempt. This breaks 
> > > > the preempt tracer selftest.
> > > > 
> > > > My solution was to just force a pass if this is detected. Perhaps 
> > > > moving the test might be better.
> > > 
> > > it would be better to just drop the BKL in that selftest. (or in all 
> > > selftests - an elevated preempt count will skew a number of things)
> > 
> > I have no problem with that, but does the BKL play any role for 
> > being held? I have no idea why it is taken in boot up, so I'm 
> > hestiant to touch it.
> 
> we can drop it in selected initcalls just fine. Its only role is 
> old-style init functions racing with other async contexts of 
> themselves.

Something like below works fine for me...

Signed-off-by: Heiko Carstens <heiko.carstens@de.ibm.com>
---

 kernel/trace/trace.c |    8 ++++++++
 1 file changed, 8 insertions(+)

Index: linux-2.6/kernel/trace/trace.c
===================================================================
--- linux-2.6.orig/kernel/trace/trace.c
+++ linux-2.6/kernel/trace/trace.c
@@ -482,6 +482,13 @@ int register_tracer(struct tracer *type)
 	}
 
 #ifdef CONFIG_FTRACE_STARTUP_TEST
+	/*
+	 * When this gets called we hold the BKL which means that preemption
+	 * is disabled. Various trace selftests however need to disable
+	 * and enable preemption for successful tests. So we drop the BKL here
+	 * and grab it after the tests again.
+	 */
+	unlock_kernel();
 	if (type->selftest) {
 		struct tracer *saved_tracer = current_trace;
 		struct trace_array *tr = &global_trace;
@@ -515,6 +522,7 @@ int register_tracer(struct tracer *type)
 		}
 		printk(KERN_CONT "PASSED\n");
 	}
+	lock_kernel();
 #endif
 
 	type->next = trace_types;

  reply	other threads:[~2008-11-18 17:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-18 12:54 Heiko Carstens
2008-11-18 13:48 ` Ingo Molnar
2008-11-18 13:49 ` Steven Rostedt
2008-11-18 13:52   ` Ingo Molnar
2008-11-18 14:32     ` Steven Rostedt
2008-11-18 14:47       ` Ingo Molnar
2008-11-18 17:06         ` Heiko Carstens [this message]
2008-11-18 17:21           ` Steven Rostedt
2008-11-18 20:55             ` Ingo Molnar
2008-11-19  9:02               ` Ingo Molnar
2008-11-19  9:23                 ` Heiko Carstens

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=20081118170635.GB4417@osiris.boeblingen.de.ibm.com \
    --to=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --cc=schwidefsky@de.ibm.com \
    /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®