public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Don Zickus <dzickus@redhat.com>
Cc: mingo@elte.hu, peterz@infradead.org, gorcunov@gmail.com,
	aris@redhat.com, linux-kernel@vger.kernel.org,
	randy.dunlap@oracle.com
Subject: Re: [PATCH 2/6] [watchdog] convert touch_softlockup_watchdog to touch_watchdog
Date: Wed, 21 Apr 2010 22:46:01 +0200	[thread overview]
Message-ID: <20100421204559.GB8677@nowhere> (raw)
In-Reply-To: <1271777043-3807-3-git-send-email-dzickus@redhat.com>

On Tue, Apr 20, 2010 at 11:23:59AM -0400, Don Zickus wrote:
> Just a scripted conversion to remove touch_softlockup_watchdog.
> 
> Also converts the once case of touch_all_softlockup_watchdogs to
> touch_all_watchdogs.
> 
> This is done as part of the removal of the old softlockup code and
> transition to the new softlockup code.
> 
> Signed-off-by: Don Zickus <dzickus@redhat.com>


In fact I worry a bit about this unification of watchdog touching.
When we touch the softlockup watchdog, do we also want to touch
the nmi watchdog?

Most of the time, I think we don't want to. We usually touch the
softlockup detector because we know we are abnormally delaying
the softlockup kthread from being scheduled, and if we are in such
situation, it means we are doing something in a sensitive context:
typically the kind of context favorable to create hardlockups...

But the opposite is right: if we touch the nmi watchdog: it means we
are abnormally delaying irqs, which means we also are abnormally
delaying the softlockup kthread from being scheduled, so if we
touch the nmi watchdog, we also want to touch the softlockup
detector.

Hence I guess we want to keep the current state:

- touch_nmi_watchdog() = touch softlockup and nmi watchdogs
- touch_softlockup_watchdog() = only touch softlockup watchdog


  reply	other threads:[~2010-04-21 20:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-20 15:23 [PATCH 0/6] lockup detector changes Don Zickus
2010-04-20 15:23 ` [PATCH 1/6] [watchdog] combine nmi_watchdog and softlockup Don Zickus
2010-04-20 15:53   ` Randy Dunlap
2010-04-20 16:11     ` Don Zickus
2010-04-21 17:27   ` Frederic Weisbecker
2010-04-21 17:50     ` Don Zickus
2010-04-21 20:24       ` Frederic Weisbecker
2010-04-21 20:49         ` Don Zickus
2010-04-20 15:23 ` [PATCH 2/6] [watchdog] convert touch_softlockup_watchdog to touch_watchdog Don Zickus
2010-04-21 20:46   ` Frederic Weisbecker [this message]
2010-04-21 21:31     ` Don Zickus
2010-04-21 21:46       ` Frederic Weisbecker
2010-04-22 13:20         ` Don Zickus
2010-04-22 18:53           ` Frederic Weisbecker
2010-04-20 15:24 ` [PATCH 3/6] [watchdog] remove old softlockup code Don Zickus
2010-04-20 15:24 ` [PATCH 4/6] [watchdog] remove nmi_watchdog.c file Don Zickus
2010-04-20 15:24 ` [PATCH 5/6] [x86] watchdog: move trigger_all_cpu_backtrace to its own die_notifier Don Zickus
2010-04-21 21:00   ` Frederic Weisbecker
2010-04-21 21:10     ` Don Zickus
2010-04-21 21:34       ` Frederic Weisbecker
2010-04-20 15:24 ` [PATCH 6/6] [x86] watchdog: cleanup hw_nmi.c cruft Don Zickus
2010-04-20 16:16 ` [PATCH 7/6] [watchdog] resolve softlockup.c conflicts Don Zickus

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=20100421204559.GB8677@nowhere \
    --to=fweisbec@gmail.com \
    --cc=aris@redhat.com \
    --cc=dzickus@redhat.com \
    --cc=gorcunov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=randy.dunlap@oracle.com \
    /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