linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] hardlockup: detect hard lockups without NMIs using secondary cpus
Date: Thu, 10 Jan 2013 15:42:58 -0800	[thread overview]
Message-ID: <20130110234258.GA15458@atomide.com> (raw)
In-Reply-To: <CAMbhsRR5azGw1-VhC4+9y7NfBPnZkBKnK34AqXdMFBsXPqdjCQ@mail.gmail.com>

* Colin Cross <ccross@android.com> [130110 14:37]:
> On Thu, Jan 10, 2013 at 12:38 PM, Tony Lindgren <tony@atomide.com> wrote:
> >
> > * Colin Cross <ccross@android.com> [130109 18:05]:
> > > +static void watchdog_check_hardlockup_other_cpu(void)
> > > +{
> > > +     int cpu;
> > > +     cpumask_t cpus = watchdog_cpus;
> > > +
> > > +     /*
> > > +      * Test for hardlockups every 3 samples.  The sample period is
> > > +      *  watchdog_thresh * 2 / 5, so 3 samples gets us back to slightly over
> > > +      *  watchdog_thresh (over by 20%).
> > > +      */
> > > +     if (__this_cpu_read(hrtimer_interrupts) % 3 != 0)
> > > +             return;
> > > +
> > > +     /* check for a hardlockup on the next cpu */
> > > +     cpu = cpumask_next(smp_processor_id(), &cpus);
> >
> > Hmm don't you want to check cpu_oneline_mask here and
> > return if the other CPU is offline?
> 
> watchdog_cpus is effectively a local copy of cpu_online_mask, but
> updated after the watchdog_nmi_touch in watchdog_nmi_enable.  This
> avoids a false positive after hotplugging in a cpu when
> cpu_online_mask is true but that cpu hasn't yet run it's first
> hrtimer.

OK thanks for clarifying that.

Tony

  reply	other threads:[~2013-01-10 23:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-10  1:57 [PATCH] hardlockup: detect hard lockups without NMIs using secondary cpus Colin Cross
2013-01-10 14:02 ` Don Zickus
2013-01-10 14:22   ` Russell King - ARM Linux
2013-01-10 16:18     ` Frederic Weisbecker
2013-01-10 17:00       ` Russell King - ARM Linux
2013-01-10 17:27   ` Colin Cross
2013-01-10 18:17     ` Don Zickus
2013-01-10 20:38 ` Tony Lindgren
2013-01-10 22:34   ` Colin Cross
2013-01-10 23:42     ` Tony Lindgren [this message]
2013-01-11  1:39 ` Liu, Chuansheng
2013-01-11  5:34   ` Colin Cross
2013-01-11  5:57     ` Liu, Chuansheng
2013-01-11  6:17       ` Colin Cross
2013-01-11  6:27         ` Liu, Chuansheng

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=20130110234258.GA15458@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).