From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
linux-kernel@vger.kernel.org,
Martin Schwidefsky <schwidefsky@de.ibm.com>
Subject: Re: ftrace: preemptoff selftest not working
Date: Tue, 18 Nov 2008 14:52:21 +0100 [thread overview]
Message-ID: <20081118135221.GE31146@elte.hu> (raw)
In-Reply-To: <alpine.DEB.1.10.0811180826510.15003@gandalf.stny.rr.com>
* 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)
Ingo
next prev parent reply other threads:[~2008-11-18 13:52 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 [this message]
2008-11-18 14:32 ` Steven Rostedt
2008-11-18 14:47 ` Ingo Molnar
2008-11-18 17:06 ` Heiko Carstens
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=20081118135221.GE31146@elte.hu \
--to=mingo@elte.hu \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--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®