From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Clark Williams <williams@redhat.com>,
"Luis Claudio R. Goncalves" <lclaudio@uudg.org>,
John Kacur <jkacur@redhat.com>,
Mike Galbraith <bitbucket@online.de>,
Joakim Hernberg <jbh@alchemy.lu>, Joe Korty <joe.korty@ccur.com>,
Muli Baron <muli.baron@gmail.com>
Subject: [PATCH RT] timer: Run irq_work() even if there are no active timers
Date: Fri, 24 Jan 2014 14:51:57 -0500 [thread overview]
Message-ID: <20140124145157.1f30d447@gandalf.local.home> (raw)
After trying hard to figure out why my i7 box was locking up with the
new active_timers code, that does not run the timer softirq if there
are no active timers, I took an extra look at the softirq handler and
noticed that it doesn't just run timer softirqs, it also runs irq work.
This was the bug that was locking up the system. It wasn't missing a
timer, it was missing irq work. By always doing the irq work callbacks,
the system boots fine.
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
diff --git a/kernel/timer.c b/kernel/timer.c
index 46467be..7c5026e 100644
--- a/kernel/timer.c
+++ b/kernel/timer.c
@@ -1464,8 +1464,12 @@ void run_local_timers(void)
raise_softirq(TIMER_SOFTIRQ);
return;
}
- if (!base->active_timers)
+ if (!base->active_timers) {
+#if defined(CONFIG_IRQ_WORK) && defined(CONFIG_PREEMPT_RT_FULL)
+ irq_work_run();
+#endif
goto out;
+ }
/* Check whether the next pending timer has expired */
if (time_before_eq(base->next_timer, jiffies))
next reply other threads:[~2014-01-24 19:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 19:51 Steven Rostedt [this message]
2014-01-24 20:09 ` [PATCH RT v2] timer: Raise softirq if there's irq_work Steven Rostedt
2014-01-24 20:20 ` Sebastian Andrzej Siewior
2014-01-24 20:35 ` Steven Rostedt
2014-01-24 20:42 ` Sebastian Andrzej Siewior
2014-01-25 0:19 ` Paul E. McKenney
2014-01-25 2:16 ` 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=20140124145157.1f30d447@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=bigeasy@linutronix.de \
--cc=bitbucket@online.de \
--cc=jbh@alchemy.lu \
--cc=jkacur@redhat.com \
--cc=joe.korty@ccur.com \
--cc=lclaudio@uudg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=muli.baron@gmail.com \
--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
all inboxes | Powered by JetHome®