From: Mike Galbraith <bitbucket@online.de>
To: paulmck@linux.vnet.ibm.com
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-rt-users@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] rcu: Eliminate softirq processing from rcutree
Date: Thu, 26 Dec 2013 11:03:32 +0100 [thread overview]
Message-ID: <1388052212.5420.4.camel@marge.simpson.net> (raw)
In-Reply-To: <1387940854.5373.8.camel@marge.simpson.net>
On Wed, 2013-12-25 at 04:07 +0100, Mike Galbraith wrote:
> On Tue, 2013-12-24 at 11:36 -0800, Paul E. McKenney wrote:
> > So which code do you think deserves the big lump of coal? ;-)
>
> Sebastian's NO_HZ_FULL locking fixes.
Whack-a-mole hasn't yet dug up any new moles.
---
kernel/timer.c | 4 ++++
1 file changed, 4 insertions(+)
Index: linux-2.6/kernel/timer.c
===================================================================
--- linux-2.6.orig/kernel/timer.c
+++ linux-2.6/kernel/timer.c
@@ -764,7 +764,9 @@ __mod_timer(struct timer_list *timer, un
timer_stats_timer_set_start_info(timer);
BUG_ON(!timer->function);
+ local_irq_disable_rt();
base = lock_timer_base(timer, &flags);
+ local_irq_enable_rt();
ret = detach_if_pending(timer, base, false);
if (!ret && pending_only)
@@ -1198,7 +1200,9 @@ static inline void __run_timers(struct t
{
struct timer_list *timer;
+ local_irq_disable_rt();
spin_lock_irq(&base->lock);
+ local_irq_enable_rt();
while (time_after_eq(jiffies, base->timer_jiffies)) {
struct list_head work_list;
struct list_head *head = &work_list;
---
kernel/time/tick-sched.c | 2 ++
1 file changed, 2 insertions(+)
Index: linux-2.6/kernel/time/tick-sched.c
===================================================================
--- linux-2.6.orig/kernel/time/tick-sched.c
+++ linux-2.6/kernel/time/tick-sched.c
@@ -216,7 +216,9 @@ void __tick_nohz_full_check(void)
static void nohz_full_kick_work_func(struct irq_work *work)
{
+ local_irq_disable_rt();
__tick_nohz_full_check();
+ local_irq_enable_rt();
}
static DEFINE_PER_CPU(struct irq_work, nohz_full_kick_work) = {
next prev parent reply other threads:[~2013-12-26 10:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-21 19:39 [PATCH] rcu: Eliminate softirq processing from rcutree Sebastian Andrzej Siewior
2013-12-22 3:07 ` Mike Galbraith
2013-12-22 8:57 ` Mike Galbraith
2013-12-23 4:38 ` Mike Galbraith
2013-12-23 5:12 ` Mike Galbraith
2014-01-24 19:46 ` Sebastian Andrzej Siewior
2014-01-25 5:20 ` Mike Galbraith
2013-12-24 19:36 ` Paul E. McKenney
2013-12-25 3:07 ` Mike Galbraith
2013-12-25 7:55 ` Paul E. McKenney
2013-12-25 17:37 ` Mike Galbraith
2014-01-17 17:14 ` Sebastian Andrzej Siewior
2014-01-18 3:25 ` Mike Galbraith
2014-01-24 19:50 ` Sebastian Andrzej Siewior
2014-01-25 5:12 ` Mike Galbraith
2014-01-27 5:10 ` Mike Galbraith
2014-01-27 16:54 ` Paul E. McKenney
2014-01-27 17:03 ` Mike Galbraith
2013-12-26 10:03 ` Mike Galbraith [this message]
2014-01-17 17:23 ` Sebastian Andrzej Siewior
2014-01-18 3:30 ` Mike Galbraith
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=1388052212.5420.4.camel@marge.simpson.net \
--to=bitbucket@online.de \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox