From: Simon Horman <horms@verge.net.au>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-sh@vger.kernel.org, Peter Zijlstra <peterz@infradead.org>,
Magnus Damm <magnus.damm@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
LAK <linux-arm-kernel@lists.infradead.org>
Subject: Re: Possible regression due to "hrtimer: Get rid of hrtimer softirq"
Date: Thu, 7 May 2015 22:25:43 +0900 [thread overview]
Message-ID: <20150507132543.GA14889@verge.net.au> (raw)
In-Reply-To: <alpine.DEB.2.11.1505071425520.4225@nanos>
Hi Thomas,
On Thu, May 07, 2015 at 02:35:59PM +0200, Thomas Gleixner wrote:
> On Thu, 7 May 2015, Simon Horman wrote:
> > ------------[ cut here ]------------
> > kernel BUG at kernel/irq_work.c:135!
>
> BUG_ON(!irqs_disabled());
>
> So something enables interrupts in the periodic tick handling
> machinery. Seems you have high resolution timers disabled, but nohz
> enabled. And that code path has a local_irq_disable/enable pair which
> causes havoc. Patch below.
Thanks for your quick response. I have been able to confirm that
when applied on top of next-20150507 the problem I observed no longer
manifests. I have successfully tested it on all the boards
where I previously observed a problem.
If you are planning to formally submit the patch below feel free to add:
Tested-by: Simon Horman <horms+renesas@verge.net.au>
> diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
> index 753c211f6195..812f7a3b9898 100644
> --- a/kernel/time/tick-sched.c
> +++ b/kernel/time/tick-sched.c
> @@ -967,11 +967,9 @@ static void tick_nohz_switch_to_nohz(void)
> if (!tick_nohz_enabled)
> return;
>
> - local_irq_disable();
> - if (tick_switch_to_oneshot(tick_nohz_handler)) {
> - local_irq_enable();
> + if (tick_switch_to_oneshot(tick_nohz_handler))
> return;
> - }
> +
> tick_nohz_active = 1;
> ts->nohz_mode = NOHZ_MODE_LOWRES;
>
> @@ -986,7 +984,6 @@ static void tick_nohz_switch_to_nohz(void)
> hrtimer_forward_now(&ts->sched_timer, tick_period);
> hrtimer_set_expires(&ts->sched_timer, next);
> tick_program_event(next, 1);
> - local_irq_enable();
> }
>
> /*
> @@ -1171,7 +1168,7 @@ void tick_oneshot_notify(void)
> * Called cyclic from the hrtimer softirq (driven by the timer
> * softirq) allow_nohz signals, that we can switch into low-res nohz
> * mode, because high resolution timers are disabled (either compile
> - * or runtime).
> + * or runtime). Called with interrupts disabled.
> */
> int tick_check_oneshot_change(int allow_nohz)
> {
>
>
>
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
next prev parent reply other threads:[~2015-05-07 13:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 11:17 Simon Horman
2015-05-07 12:35 ` Thomas Gleixner
2015-05-07 13:25 ` Simon Horman [this message]
2015-05-08 17:14 ` Kevin Hilman
2015-05-08 9:25 ` [tip:timers/core] nohz: Fix !HIGH_RES_TIMERS hang tip-bot for Thomas Gleixner
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=20150507132543.GA14889@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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
Powered by JetHome