From: Ingo Molnar <mingo@elte.hu>
To: Andrew Morton <akpm@osdl.org>
Cc: rmk+lkml@arm.linux.org.uk, linux-kernel@vger.kernel.org
Subject: Re: [patch] fix emergency reboot: call reboot notifier list if possible
Date: Wed, 17 Jan 2007 11:25:11 +0100 [thread overview]
Message-ID: <20070117102510.GA20917@elte.hu> (raw)
In-Reply-To: <20070117020343.8622e44d.akpm@osdl.org>
* Andrew Morton <akpm@osdl.org> wrote:
> Making it dependent upon CONFIG_PREEMPT seems a bit sucky. Perhaps
> pass in some "you were called from /proc/sysrq-trigger" notification?
looks quite invasive to the whole sysrq interfaces, it trickles all the
way down into sysrq.c's handler prototype, affecting 20 prototypes.
Worth the trouble?
> Also, there are ways of telling if the kernel has oopsed (oops
> counter, oops_in_progress, etc) which should perhaps be tested.
i'm not sure. Should we perhaps forget this patch and only do the
i386/x86_64 VMX patch i sent?
> Or just learn to type `reboot -fn' ;)
well, emergency_reboot() might also be called from panic(), if someone
sets panic_timeout, resulting in a similar hang. It might be called from
a serial console on a soft-locked-up system, having no physical access
to the system. Having a hung reboot in that scenario is not really
productive.
Ingo
next prev parent reply other threads:[~2007-01-17 10:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 9:13 [patch] fix emergency reboot: call reboot notifier list if possible Ingo Molnar
2007-01-17 9:22 ` Russell King
2007-01-17 9:39 ` Ingo Molnar
2007-01-17 10:03 ` Andrew Morton
2007-01-17 10:25 ` Ingo Molnar [this message]
2007-01-23 19:57 ` Pavel Machek
2007-01-24 16:30 ` Randy Dunlap
2007-01-24 17:49 ` linux-os (Dick Johnson)
2007-01-17 9:51 ` [patch] KVM: do VMXOFF upon reboot Ingo Molnar
2007-01-17 10:02 ` Ingo Molnar
2007-01-21 10:17 ` Avi Kivity
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=20070117102510.GA20917@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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.