From: Muli Baron <muli.baron@gmail.com>
To: linux-rt-users@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] 3.12.6-rt9
Date: Tue, 21 Jan 2014 08:39:10 +0200 [thread overview]
Message-ID: <52DE160E.7080504@gmail.com> (raw)
In-Reply-To: <20140120211736.0c97418a@gandalf.local.home>
On 21/1/2014 04:17, Steven Rostedt wrote:
> On Sat, 18 Jan 2014 04:15:29 +0100
> Mike Galbraith <bitbucket@online.de> wrote:
>
>
>>> So you also have the timers-do-not-raise-softirq-unconditionally.patch?
>>
>
> People have been complaining that the latest 3.12-rt does not boot on
> intel i7 boxes. And by reverting this patch, it boots fine.
>
> I happen to have a i7 box to test on, and sure enough, the latest
> 3.12-rt locks up on boot and reverting the
> timers-do-not-raise-softirq-unconditionally.patch, it boots fine.
>
> Looking into it, I made this small update, and the box boots. Seems
> checking "active_timers" is not enough to skip raising softirqs. I
> haven't looked at why yet, but I would like others to test this patch
> too.
>
> I'll leave why this lets i7 boxes boot as an exercise for Thomas ;-)
>
> -- Steve
>
> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
>
> diff --git a/kernel/timer.c b/kernel/timer.c
> index 46467be..8212c10 100644
> --- a/kernel/timer.c
> +++ b/kernel/timer.c
> @@ -1464,13 +1464,11 @@ void run_local_timers(void)
> raise_softirq(TIMER_SOFTIRQ);
> return;
> }
> - if (!base->active_timers)
> - goto out;
>
> /* Check whether the next pending timer has expired */
> if (time_before_eq(base->next_timer, jiffies))
> raise_softirq(TIMER_SOFTIRQ);
> -out:
> +
> rt_spin_unlock_after_trylock_in_irq(&base->lock);
>
> }
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
While this might fix booting on i7 machines it kinds of defeats the
original purpose of this patch, which was to let NO_HZ_FULL work
properly with threaded interrupts. With the active_timers check removed
the timer interrupt keeps firing even though there is only one task
running on a specific processor, since it can't shut down the tick
because the ksoftirqd thread keeps getting scheduled (see the previous
thread "CONFIG_NO_HZ_FULL + CONFIG_PREEMPT_RT_FULL = nogo" for the full
discussion).
-- Muli
next prev parent reply other threads:[~2014-01-21 6:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-23 22:50 [ANNOUNCE] 3.12.6-rt9 Sebastian Andrzej Siewior
2013-12-24 15:15 ` 3.12.6-rt9 build failure Nicholas Mc Guire
2013-12-24 15:47 ` [ANNOUNCE] 3.12.6-rt9 Mike Galbraith
2013-12-24 16:39 ` Pavel Vasilyev
2013-12-25 3:24 ` Mike Galbraith
2013-12-25 3:24 ` Mike Galbraith
2014-01-17 17:00 ` Sebastian Andrzej Siewior
2014-01-17 17:00 ` Sebastian Andrzej Siewior
2014-01-18 3:15 ` Mike Galbraith
2014-01-21 2:17 ` Steven Rostedt
2014-01-21 6:39 ` Muli Baron [this message]
2014-01-21 15:40 ` Joe Korty
2014-01-22 21:27 ` Joakim Hernberg
2014-01-24 11:19 ` Sebastian Andrzej Siewior
2013-12-27 20:00 ` Nicholas Mc Guire
2013-12-28 3:30 ` Mike Galbraith
2013-12-28 3:48 ` Mike Galbraith
2013-12-28 7:43 ` Nicholas Mc Guire
2013-12-28 13:57 ` Mike Galbraith
2013-12-28 4:33 ` Mike Galbraith
2014-01-11 20:25 ` Joakim Hernberg
2014-01-17 16:10 ` Sebastian Andrzej Siewior
2014-01-19 20:54 ` Fernando Lopez-Lezcano
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=52DE160E.7080504@gmail.com \
--to=muli.baron@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.