mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Don Zickus <dzickus@redhat.com>
Cc: <x86@kernel.org>, Peter Zijlstra <peterz@infradead.org>,
	jwjstone@fastmail.fm, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2 v2] watchdog, nmi:  Allow hardlockup to panic by default
Date: Thu, 17 Mar 2011 18:50:13 -0700	[thread overview]
Message-ID: <20110317185013.7c8be1e0.akpm@linux-foundation.org> (raw)
In-Reply-To: <1299533860-1642-1-git-send-email-dzickus@redhat.com>

On Mon,  7 Mar 2011 16:37:39 -0500 Don Zickus <dzickus@redhat.com> wrote:

> Add a Kconfig option to allow users to set the hardlockup to panic
> by default.  Also add in a 'nmi_watchdog=nopanic' to override this.
> 

Changelog forgot to tell us "why".

>  			Format: [state][,regs][,debounce][,die]
>  
>  	nmi_watchdog=	[KNL,BUGS=X86] Debugging features for SMP kernels
> -			Format: [panic,][num]
> +			Format: [panic,][nopanic,][num]

It would be better to support panic=[0|1], if that can be simply done
in a back-compatible fashion.

>  static int __init hardlockup_panic_setup(char *str)
>  {
>  	if (!strncmp(str, "panic", 5))
>  		hardlockup_panic = 1;
> +	else if (!strncmp(str, "nopanic", 5))

s/5/7/

> +		hardlockup_panic = 0;
>  	else if (!strncmp(str, "0", 1))
>  		watchdog_enabled = 0;
>  	return 1;


  parent reply	other threads:[~2011-03-18  1:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-07 21:37 Don Zickus
2011-03-07 21:37 ` [PATCH 2/2 v2] watchdog: Always return NOTIFY_OK during cpu up/down events Don Zickus
2011-03-17  9:12   ` Peter Zijlstra
2011-03-17 12:16   ` WANG Cong
2011-03-17  9:12 ` [PATCH 1/2 v2] watchdog, nmi: Allow hardlockup to panic by default Peter Zijlstra
2011-03-17 12:05 ` WANG Cong
2011-03-18  1:50 ` Andrew Morton [this message]
2011-03-18 17:19   ` Don Zickus
2011-03-18 18:23     ` Andrew Morton
2011-03-18 18:58       ` 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=20110317185013.7c8be1e0.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dzickus@redhat.com \
    --cc=jwjstone@fastmail.fm \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=x86@kernel.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

Powered by JetHome