From: Sasha Levin <levinsasha928@gmail.com>
To: paulmck@linux.vnet.ibm.com
Cc: Sasha Levin <sasha.levin@oracle.com>,
Steven Rostedt <rostedt@goodmis.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
paul.gortmaker@windriver.com, Dave Jones <davej@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: irq_work: WARNING: at kernel/irq_work.c:98 irq_work_needs_cpu+0x8a/0xb0()
Date: Sun, 10 Mar 2013 14:48:08 -0400 [thread overview]
Message-ID: <513CD568.90409@gmail.com> (raw)
In-Reply-To: <20130308222058.GP3268@linux.vnet.ibm.com>
On 03/08/2013 05:20 PM, Paul E. McKenney wrote:
> Alternatively, given that this is a debug option, how about replacing
> the schedule_timeout_uninterruptible() with something like the following:
>
> {
> unsigned long starttime = jiffies + 2;
>
> while (ULONG_CMP_LT(jiffies, starttime))
> cpu_relax();
> }
>
> That way the RCU GP kthread would never go to sleep, and thus would not
> have to wait for the timer to wake it up. If this works, then my next
> thought would be to try to get at the timer state for the wakeup fo
> schedule_timeout_uninterruptible().
It did the trick, I still see those IRQ warnings but the RCU lockup
is gone.
Thanks,
Sasha
next prev parent reply other threads:[~2013-03-10 18:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 5:48 irq_work: WARNING: at kernel/irq_work.c:98 irq_work_needs_cpu+0x8a/0xb0() Sasha Levin
2013-03-08 16:44 ` Paul E. McKenney
2013-03-08 18:24 ` Sasha Levin
2013-03-08 19:46 ` Paul E. McKenney
2013-03-08 20:48 ` Sasha Levin
2013-03-08 22:20 ` Paul E. McKenney
2013-03-10 18:48 ` Sasha Levin [this message]
2013-03-10 21:04 ` Paul E. McKenney
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=513CD568.90409@gmail.com \
--to=levinsasha928@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paul.gortmaker@windriver.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=sasha.levin@oracle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox