From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Fengguang Wu <fengguang.wu@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
john stultz <johnstul@us.ibm.com>, Ingo Molnar <mingo@elte.hu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: lockdep WARNING for run_timer_softirq()
Date: Wed, 05 Sep 2012 19:09:07 +0200 [thread overview]
Message-ID: <1346864947.2600.33.camel@twins> (raw)
In-Reply-To: <1346854836.27919.51.camel@gandalf.local.home>
On Wed, 2012-09-05 at 10:20 -0400, Steven Rostedt wrote:
> Well, the branch tracer was active. That means all 'if()'s were being
> traced. It comes down to how you define 'if' ;-)
Yeah, I tried making an argument for:
we tell lockdep irqs are enabled hit an if() end up in lockdep code
through the branch tracer and find borken state, or vice-versa.
Just couldn't find it in the provided stack-trace. Might be I didn't
look hard enough, might be there's something else entirely.
All I know is I've never seen it on real hardware, then again, I hardly
ever have CONFIG_PARAVIRT or CONFIG_TRACE_BRANCH_PROFILING, let alone
both.
next prev parent reply other threads:[~2012-09-05 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-31 7:21 lockdep WARNING for run_timer_softirq() Fengguang Wu
2012-08-31 7:32 ` Fengguang Wu
2012-09-05 11:47 ` Peter Zijlstra
2012-09-05 14:20 ` Steven Rostedt
2012-09-05 17:09 ` Peter Zijlstra [this message]
2012-09-05 17:14 ` Steven Rostedt
2012-09-05 17:19 ` Peter Zijlstra
2012-09-05 19:23 ` 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=1346864947.2600.33.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=fengguang.wu@intel.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.