From: Peter Zijlstra <peterz@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Clark Williams <williams@redhat.com>
Subject: Re: [RFC][PATCH] preempt: Debug for possible missed preemption checks
Date: Fri, 17 Jan 2014 10:08:56 +0100 [thread overview]
Message-ID: <20140117090856.GE11314@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <20140116211214.581197e5.akpm@linux-foundation.org>
On Thu, Jan 16, 2014 at 09:12:14PM -0800, Andrew Morton wrote:
> On Thu, 16 Jan 2014 23:57:51 -0500 Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > When PROVE_LOCKING and PREEMPT is configured, the preempt state
> > tracking is active. Testing this out, I added a module that did the
> > following:
>
> So I assume your kernel at least has no instances of this bug, so we
> don't need the patch ;) It *is* a fairly daft thing to do.
Yeah, its exceedingly daft, but I do run into it every so often. Say
once a year or so.
Also, its usually not really a problem on 'normal' kernels, but it
absolutely blows on -rt.
next prev parent reply other threads:[~2014-01-17 9:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 4:57 [RFC][PATCH] preempt: Debug for possible missed preemption checks Steven Rostedt
2014-01-17 5:12 ` Andrew Morton
2014-01-17 9:08 ` Peter Zijlstra [this message]
2014-01-18 23:44 ` Steven Rostedt
2014-01-19 0:52 ` Stephen Rothwell
2014-01-19 1:08 ` Steven Rostedt
2014-01-21 23:50 ` Stephen Rothwell
2014-01-22 19:47 ` Paul Gortmaker
2014-01-22 20:09 ` 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=20140117090856.GE11314@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=williams@redhat.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