All of lore.kernel.org
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: Anton Blanchard <anton@samba.org>
Cc: uobergfe@redhat.com, drjones@redhat.com,
	akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: Confusing behaviour with /proc/sys/kernel/nmi_watchdog
Date: Wed, 5 Nov 2014 09:53:56 -0500	[thread overview]
Message-ID: <20141105145356.GL135937@redhat.com> (raw)
In-Reply-To: <20141105093420.1c7500d8@kryten>

On Wed, Nov 05, 2014 at 09:34:20AM +1100, Anton Blanchard wrote:
> 
> Hi,
> 
> commit 9919e39a1738 ("kvm: ensure hard lockup detection is disabled by
> default") provided a way for the kernel to disable the hard lockup
> detector at runtime.
> 
> I'm using it on ppc64 but notice some weird behaviour with the
> nmi_watchdog procfs variable. At boot, that the hard lockup
> detector appears to be enabled even when we disable it via
> watchdog_enable_hardlockup_detector(false):
> 
> # cat /proc/sys/kernel/nmi_watchdog 
> 1
> 
> I have to echo 0 to it then echo 1 again to enable it.

Hi Anton,

I believe Andrew answered the question for you, it's a WIP and we have
patches to clean that up.

I don't see ppc64 watchdog support in arch/powerpc, is that something you
are working with on implementing?

Cheers,
Don

  parent reply	other threads:[~2014-11-05 14:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 22:34 Confusing behaviour with /proc/sys/kernel/nmi_watchdog Anton Blanchard
2014-11-05 10:26 ` Andrew Jones
2015-01-21  3:39   ` Anton Blanchard
2015-01-21 10:52     ` Andrew Jones
2015-01-21 14:30       ` Don Zickus
2014-11-05 14:53 ` Don Zickus [this message]
2014-11-05 18:53   ` Anton Blanchard

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=20141105145356.GL135937@redhat.com \
    --to=dzickus@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=anton@samba.org \
    --cc=drjones@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=uobergfe@redhat.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 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.