LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Don Zickus <dzickus@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Ulrich Obergfell <uobergfe@redhat.com>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 7/9] watchdog: enable the new user interface of the watchdog mechanism
Date: Mon, 23 Feb 2015 13:19:46 -0800	[thread overview]
Message-ID: <20150223131946.599d3af2a361b4fd70df0edf@linux-foundation.org> (raw)
In-Reply-To: <1423168825-156238-8-git-send-email-dzickus@redhat.com>

On Thu,  5 Feb 2015 15:40:23 -0500 Don Zickus <dzickus@redhat.com> wrote:

> From: Ulrich Obergfell <uobergfe@redhat.com>
> 
> With the current user interface of the watchdog mechanism it is only
> possible to disable or enable both lockup detectors at the same time.
> This series introduces new kernel parameters and changes the semantics
> of some existing kernel parameters, so that the hard lockup detector
> and the soft lockup detector can be disabled or enabled individually.
> With this series applied, the user interface is as follows.
> 
> - parameters in /proc/sys/kernel
> 
>   . soft_watchdog
>     This is a new parameter to control and examine the run state of
>     the soft lockup detector.
> 
>   . nmi_watchdog
>     The semantics of this parameter have changed. It can now be used
>     to control and examine the run state of the hard lockup detector.
> 
>   . watchdog
>     This parameter is still available to control the run state of both
>     lockup detectors at the same time. If this parameter is examined,
>     it shows the logical OR of soft_watchdog and nmi_watchdog.
> 
>   . watchdog_thresh
>     The semantics of this parameter are not affected by the patch.
> 
> - kernel command line parameters
> 
>   . nosoftlockup
>     The semantics of this parameter have changed. It can now be used
>     to disable the soft lockup detector at boot time.
> 
>   . nmi_watchdog=0 or nmi_watchdog=1
>     Disable or enable the hard lockup detector at boot time. The patch
>     introduces '=1' as a new option.
> 
>   . nowatchdog
>     The semantics of this parameter are not affected by the patch. It
>     is still available to disable both lockup detectors at boot time.

So we need a whole bunch of updates and additions to Documentation/?

Are all these changes back-compatible with previous kernel versions?



  reply	other threads:[~2015-02-23 21:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-05 20:40 [PATCH 0/9] watchdog: internally split softlockup and hardlockup Don Zickus
2015-02-05 20:40 ` [PATCH 1/9] watchdog: new definitions and variables, initialization Don Zickus
2015-02-05 20:40 ` [PATCH 2/9] watchdog: introduce the proc_watchdog_update() function Don Zickus
2015-02-05 20:40 ` [PATCH 3/9] watchdog: move definition of 'watchdog_proc_mutex' outside of proc_dowatchdog() Don Zickus
2015-02-05 20:40 ` [PATCH 4/9] watchdog: introduce the proc_watchdog_common() function Don Zickus
2015-02-05 20:40 ` [PATCH 5/9] watchdog: introduce separate handlers for parameters in /proc/sys/kernel Don Zickus
2015-02-05 20:40 ` [PATCH 6/9] watchdog: implement error handling for failure to set up hardware perf events Don Zickus
2015-02-23 21:17   ` Andrew Morton
2015-02-24 15:39     ` Don Zickus
2015-03-02 19:06     ` Don Zickus
2015-02-05 20:40 ` [PATCH 7/9] watchdog: enable the new user interface of the watchdog mechanism Don Zickus
2015-02-23 21:19   ` Andrew Morton [this message]
2015-02-24 15:46     ` Don Zickus
2015-03-02 19:05     ` [PATCH 7/9 UPDATE] " Don Zickus
2015-02-05 20:40 ` [PATCH 8/9] watchdog: clean up some function names and arguments Don Zickus
2015-02-05 20:40 ` [PATCH 9/9] watchdog: introduce the hardlockup_detector_disable() function Don Zickus
2015-02-05 23:22 ` [PATCH 0/9] watchdog: internally split softlockup and hardlockup Andrew Morton
2015-02-06 14:12   ` Don Zickus
  -- strict thread matches above, loose matches on Subject: below --
2014-11-04 16:20 Don Zickus
2014-11-04 16:20 ` [PATCH 7/9] watchdog: enable the new user interface of the watchdog mechanism 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=20150223131946.599d3af2a361b4fd70df0edf@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dzickus@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=uobergfe@redhat.com \
    --subject='Re: [PATCH 7/9] watchdog: enable the new user interface of the watchdog mechanism' \
    /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

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).