linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jason Baron <jbaron@akamai.com>,
	benh@kernel.crashing.org, paulus@samba.org, ralf@linux-mips.org,
	linux-kernel@vger.kernel.org,
	Felipe Contreras <felipe.contreras@gmail.com>
Subject: Re: [PATCH v2] panic: Make panic_timeout configurable
Date: Tue, 19 Nov 2013 08:15:31 +0100	[thread overview]
Message-ID: <20131119071531.GA32469@gmail.com> (raw)
In-Reply-To: <20131118143059.afe17d2faced16171a05eb10@linux-foundation.org>


* Andrew Morton <akpm@linux-foundation.org> wrote:

> On Mon, 18 Nov 2013 21:04:36 +0000 (GMT) Jason Baron <jbaron@akamai.com> wrote:
> 
> > The panic_timeout value can be set via the command line option 'panic=x', or via
> > /proc/sys/kernel/panic, however that is not sufficient when the panic occurs
> > before we are able to set up these values. Thus, add a CONFIG_PANIC_TIMEOUT
> > so that we can set the desired value from the .config.
> > 
> > The default panic_timeout value continues to be 0 - wait forever, except for
> > powerpc and mips, which have been defaulted to 180 and 5 respectively. This
> > is in keeping with the fact that these arches already set panic_timeout in
> > their arch init code. However, I found three exceptions- two in mips and one in
> > powerpc where the settings didn't match these default values. In those cases, I
> > left the arch code so it continues to override, in case the user has not changed
> > from the default. It would nice if these arches had one default value, or if we
> > could determine the correct setting at compile-time.
> 
> Felipe is proposing a simpler patch ("panic: setup panic_timeout
> early") which switches to early_param().  Is that sufficient for the
> (undescribed!) failure which you are presumably observing?

Also note that that patch is still incomplete: if panic_timeout is 
switched to early_param() then closely related functionality such as 
pause_on_oops should be moved early as well...

Thanks,

	Ingo

  parent reply	other threads:[~2013-11-19  7:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 21:04 [PATCH v2] panic: Make panic_timeout configurable Jason Baron
2013-11-18 22:30 ` Andrew Morton
2013-11-18 23:13   ` Jason Baron
2013-11-19  7:09     ` Ingo Molnar
2013-11-19 22:04       ` Jason Baron
2013-11-21 11:16         ` Michael Ellerman
2013-11-21 21:21           ` Jason Baron
2013-11-22  1:54             ` Michael Ellerman
2013-11-19  7:15   ` Ingo Molnar [this message]
2013-11-27  6:13     ` Felipe Contreras
2013-11-19  9:02 ` Ralf Baechle
2013-11-19 14:51   ` Shinya Kuribayashi
2013-11-19 16:38     ` Ralf Baechle
2013-11-19 17:11   ` Jason Baron
2013-11-19 17:22     ` Ralf Baechle
2013-11-21  8:44   ` Jayachandran C.

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=20131119071531.GA32469@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=benh@kernel.crashing.org \
    --cc=felipe.contreras@gmail.com \
    --cc=jbaron@akamai.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=ralf@linux-mips.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;
as well as URLs for NNTP newsgroup(s).