From: Russell King <rmk@arm.linux.org.uk>
To: linux-arch@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: pause_on_oops
Date: Sun, 17 Jun 2007 12:47:58 +0100 [thread overview]
Message-ID: <20070617114758.GA6716@flint.arm.linux.org.uk> (raw)
Folk,
It seems that arch maintainers weren't copied on the "pause on oops"
patch (dd287796d608fcdc3fe5e8fdb5bf762a8f1bc32a) which introduced
some generic infrastructure (oops_enter, oops_exit). This has been
subsequently used by lockdep to disable itself when an oops occurs.
AFAICS only i386, powerpc and x86_64 call oops_enter() and oops_exit().
However, ARM, MIPS, S390, SH, Sparc64, and UML support lockdep, so
presumably it would be a good idea if they too were aware of these
functions.
I suggest _at least_ mips, s390, sh, sparc64 and uml folk look into
adding support to their die() functions (and check whether their
die functions are missing any other useful functionality.)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next reply other threads:[~2007-06-17 11:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-17 11:47 Russell King [this message]
2007-06-18 10:03 ` pause_on_oops Paul Mundt
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=20070617114758.GA6716@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.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;
as well as URLs for NNTP newsgroup(s).