From: Peter Zijlstra <peterz@infradead.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [sched/preempt] INFO: rcu_sched self-detected stall on CPU { 1}
Date: Thu, 6 Feb 2014 12:27:31 +0100 [thread overview]
Message-ID: <20140206112731.GH4941@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20140206095646.GE17971@localhost>
On Thu, Feb 06, 2014 at 05:56:46PM +0800, Fengguang Wu wrote:
> Hi Peter,
>
> We noticed the below RCU stalls which will block the system.
> The problem is bisected to
>
> commit 8cb75e0c4ec9786b81439761eac1d18d4a931af3
> Author: Peter Zijlstra <peterz@infradead.org>
> AuthorDate: Wed Nov 20 12:22:37 2013 +0100
> Commit: Ingo Molnar <mingo@kernel.org>
> CommitDate: Mon Jan 13 17:38:55 2014 +0100
>
> sched/preempt: Fix up missed PREEMPT_NEED_RESCHED folding
>
> arch/x86/include/asm/mwait.h | 2 +-
> include/linux/preempt.h | 15 +++++++++++++++
> include/linux/sched.h | 15 +++++++++++++++
> kernel/cpu/idle.c | 17 ++++++++++-------
> kernel/sched/core.c | 3 +--
> 5 files changed, 42 insertions(+), 10 deletions(-)
>
> [ 85.786775] INFO: rcu_sched self-detected stall on CPU { 1} (t=15000 jiffies g=233 c=232 q=1940)
Did the initial kernel contain the below?
---
commit 215393bc1fab3d61a5a296838bdffce22f27ffda
Author: Peter Zijlstra <peterz@infradead.org>
Date: Wed Jan 22 11:24:35 2014 +0100
sched/preempt/x86: Fix voluntary preempt for x86
The #ifdef CONFIG_PREEMPT is both not needed and wrong.
Its not required because asm/preempt.h should provide
{set,clear}_preempt_need_resched() regardless and its wrong because
for voluntary preempt we still rely on PREEMPT_NEED_RESCHED.
Reported-and-Tested-by: Markus Trippelsdorf <markus@trippelsdorf.de>
Fixes: 8cb75e0c4ec9 ("sched/preempt: Fix up missed PREEMPT_NEED_RESCHED folding")
Signed-off-by: Peter Zijlstra <peterz@infradead.org>
Cc: Dipankar Sarma <dipankar@in.ibm.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Link: http://lkml.kernel.org/r/20140122102435.GH31570@twins.programming.kicks-ass.net
Signed-off-by: Ingo Molnar <mingo@kernel.org>
diff --git a/include/linux/preempt.h b/include/linux/preempt.h
index 59749fc..de83b4e 100644
--- a/include/linux/preempt.h
+++ b/include/linux/preempt.h
@@ -134,7 +134,6 @@ do { \
#undef preempt_check_resched
#endif
-#ifdef CONFIG_PREEMPT
#define preempt_set_need_resched() \
do { \
set_preempt_need_resched(); \
@@ -144,10 +143,6 @@ do { \
if (tif_need_resched()) \
set_preempt_need_resched(); \
} while (0)
-#else
-#define preempt_set_need_resched() do { } while (0)
-#define preempt_fold_need_resched() do { } while (0)
-#endif
#ifdef CONFIG_PREEMPT_NOTIFIERS
next prev parent reply other threads:[~2014-02-06 11:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 9:56 Fengguang Wu
2014-02-06 11:27 ` Peter Zijlstra [this message]
2014-02-06 11:46 ` Fengguang Wu
2014-02-06 11:53 ` Fengguang Wu
2014-02-06 12:08 ` Bockholdt Arne
2014-02-06 12:19 ` Peter Zijlstra
2014-02-07 7:06 ` Bockholdt Arne
2014-02-12 6:28 ` Bockholdt Arne
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=20140206112731.GH4941@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.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®