From: Meelis Roos <mroos@linux.ee>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Borislav Petkov <bp@alien8.de>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Len Brown <lenb@kernel.org>, "Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: 3.10-rc3: WARNING: at kernel/time/tick-broadcast.c:578
Date: Mon, 27 May 2013 18:53:08 +0300 (EEST) [thread overview]
Message-ID: <alpine.SOC.1.00.1305271849130.2372@math.ut.ee> (raw)
In-Reply-To: <alpine.LFD.2.02.1305271456280.4220@ionos>
> > On Mon, May 27, 2013 at 02:09:33PM +0300, Meelis Roos wrote:
> > > I enabled the new full dynctick on one of my test PCs - Intel 815
> >
> > Do you mean CONFIG_NO_HZ_FULL? If so, it is not enabled in the .config
> > below.
Yes. I meant that - but obviously I did not enable it on this machine. I
enabled it on every machine wehere this was offered for me by make
oldconfig.
> > Also, there are a bunch of timers fixes from Thomas in tip - you could
> > try to merge tip/master ontop of -rc3 and retest.
>
> All related fixes are already in Linus tree.
OK, will not check tip/master.
> That brilliant cpuidle stuff calls
> clockevents_notify(CLOCK_EVT_NOTIFY_BROADCAST_ENTER) twice. So what happens is:
>
> CPU0 CPU1
> cpuidle_idle_call()
> clockevents_notify(CLOCK_EVT_NOTIFY_BROADCAST_ENTER)
> set cpu in tick_broadcast_oneshot_mask
> broadcast interrupt
> event expired for cpu1
> set pending bit
> acpi_idle_enter_simple()
> clockevents_notify(CLOCK_EVT_NOTIFY_BROADCAST_ENTER)
> WARN_ON(pending bit)
>
> So we need to move the WARN_ON into the section where we actually set
> the broadcast stuff up.
Are you sure? This is a UP machine.
Tested the patch - no effect, warning is still there :(
> diff --git a/kernel/time/tick-broadcast.c b/kernel/time/tick-broadcast.c
> index 24938d5..ec21dc0 100644
> --- a/kernel/time/tick-broadcast.c
> +++ b/kernel/time/tick-broadcast.c
> @@ -575,8 +575,8 @@ void tick_broadcast_oneshot_control(unsigned long reason)
>
> raw_spin_lock_irqsave(&tick_broadcast_lock, flags);
> if (reason == CLOCK_EVT_NOTIFY_BROADCAST_ENTER) {
> - WARN_ON_ONCE(cpumask_test_cpu(cpu, tick_broadcast_pending_mask));
> if (!cpumask_test_and_set_cpu(cpu, tick_broadcast_oneshot_mask)) {
> + WARN_ON_ONCE(cpumask_test_cpu(cpu, tick_broadcast_pending_mask));
> clockevents_set_mode(dev, CLOCK_EVT_MODE_SHUTDOWN);
> /*
> * We only reprogram the broadcast timer if we
>
--
Meelis Roos (mroos@ut.ee) http://www.cs.ut.ee/~mroos/
next prev parent reply other threads:[~2013-05-27 15:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 11:09 Meelis Roos
2013-05-27 12:35 ` Borislav Petkov
2013-05-27 13:38 ` Thomas Gleixner
2013-05-27 15:53 ` Meelis Roos [this message]
2013-05-27 16:44 ` Thomas Gleixner
2013-05-27 17:06 ` Meelis Roos
2013-05-28 7:50 ` [tip:timers/urgent] tick: Cure broadcast false positive pending bit warning 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=alpine.SOC.1.00.1305271849130.2372@math.ut.ee \
--to=mroos@linux.ee \
--cc=bp@alien8.de \
--cc=fweisbec@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
--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
all inboxes | Powered by JetHome®