All of lore.kernel.org
 help / color / mirror / Atom feed
From: dzickus@redhat.com (Don Zickus)
To: linux-arm-kernel@lists.infradead.org
Subject: mpcore watchdogs questions
Date: Mon, 6 Dec 2010 08:56:11 -0500	[thread overview]
Message-ID: <20101206135611.GC21786@redhat.com> (raw)
In-Reply-To: <AANLkTikRbF9yVUMLo2rRfM0zC2GRRhA7MD7dyCMR2+Sm@mail.gmail.com>

On Mon, Dec 06, 2010 at 10:34:31AM +0100, Per Fransson wrote:
> 
> The way I see it, the idea behind the lockup detection code, and please correct
> me if I'm wrong, is to cover the following case on a per-CPU basis:
> 
> * Assuming the CPU in question is actually chugging along, is it
> getting real work
> done, where "real work" is defined as being able to schedule a high-prio kernel
> thread and have it perform the actions expected of it (kicking the watchdog).
> In the hardlockup case "real work" is instead defined as being able to
> respond to
> hrtimers going off.

Yup, that sounds right.

Cheers,
Don

      reply	other threads:[~2010-12-06 13:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-03 13:56 mpcore watchdogs questions Per Fransson
2010-12-03 14:58 ` Don Zickus
2010-12-06  9:34   ` Per Fransson
2010-12-06 13:56     ` Don Zickus [this message]

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=20101206135611.GC21786@redhat.com \
    --to=dzickus@redhat.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 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.