From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: hidave.darkstar@gmail.com, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org
Subject: Re: [PATCH v3] printk: add halt_delay parameter for printk delay in halt phase
Date: Tue, 9 Jun 2009 00:02:53 +0200 [thread overview]
Message-ID: <20090608220253.GD22049@elte.hu> (raw)
In-Reply-To: <20090608143913.749e19c5.akpm@linux-foundation.org>
* Andrew Morton <akpm@linux-foundation.org> wrote:
> On Mon, 8 Jun 2009 19:15:01 +0200
> Ingo Molnar <mingo@elte.hu> wrote:
>
> > > questions: is it possible for interrupts to be disabled at this
> > > time? If so, can we get an NMI watchdog hit?
> >
> > no, we generally turn off the nmi watchdog during shutdown,
> > disable the lapic and io-apic, etc.
>
> Is x86 the only architecture which implements an NMI watchdog?
Sparc64 does too IIRC.
> > > Is the softlockup detector still running and if so, can it
> > > trigger?
> >
> > in (non-emergency) reboot, last i checked, we stopped all other
> > CPUs first, and then killed the current one. There's no chance
> > for the watchdog thread to run.
>
> OK, but... See below.
>
> > Anyway ... you seem to be uncomfortable about this patch -
> > should i delay it for now to let it all play out? We are close
> > to the merge window.
>
> I'm OK - I'm just bouncing ideas and questions off you guys, to
> make sure that we've thought this through all the way.
>
> Here's another: why is it a boot option rather than a
> runtime-tunable? A /proc tweakable is generally preferable because
> it avoids the oh-crap-i-forgot-to-edit-grub.conf thing. And we
> could perhaps then remove all those system_state tests: userspace
> sets printk_delay immediately prior to running halt/reboot/etc?
>
> Plus the feature becomes more general - perhaps there are use
> cases where people want to slow down printks, such as: kernel goes
> oops, data scrolls off, serial console/netconsole unavailable.
> pause_on_oops is supposed to help here but last time I tried it,
> it kinda didn't work, plus pause_on_oops doesn't solve the
> data-scrolled-off problem.
>
> Thirdly, if we do this as a general /proc/printk_delay thing,
> perhaps it can be consolidated with the existing boot_delay=
> implementation.
Consolidatig with the existing boot delay implementation was one of
my first suggestions.
The /proc thing definitely makes sense - the boot option was just
symmetry to the existing boot-delay approach.
I've unapplied this patch - i agree that it needs a bit more work
and i dont want to hold up other changes in the core/printk branch.
Ingo
next prev parent reply other threads:[~2009-06-08 22:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 7:40 [PATCH v3] printk: add halt_delay parameter for printk delay in halt phase Dave Young
2009-06-08 8:12 ` [tip:core/printk] printk: Add halt_delay=<msecs> " tip-bot for Dave Young
2009-06-08 8:14 ` [PATCH v3] printk: add halt_delay " Ingo Molnar
2009-06-08 8:28 ` Andrew Morton
2009-06-08 8:42 ` Dave Young
2009-06-08 8:48 ` Ingo Molnar
2009-06-08 16:26 ` Andrew Morton
2009-06-08 17:15 ` Ingo Molnar
2009-06-08 21:39 ` Andrew Morton
2009-06-08 22:02 ` Ingo Molnar [this message]
2009-06-08 22:07 ` Andrew Morton
2009-06-08 22:12 ` Ingo Molnar
2009-06-09 1:01 ` Dave Young
2009-06-09 1:35 ` Dave Young
2009-06-09 2:33 ` Andrew Morton
2009-06-09 0:48 ` Dave Young
2009-06-08 8:37 ` Dave Young
2009-06-08 8:46 ` Ingo Molnar
2009-06-08 8:56 ` Dave Young
2009-06-08 8:58 ` Ingo Molnar
2009-06-08 9:00 ` Dave Young
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=20090608220253.GD22049@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=hidave.darkstar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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