From: Russell King <rmk@arm.linux.org.uk>
To: David VomLehn <dvomlehn@cisco.com>
Cc: to@dvomlehn-lnx2.corp.sa.net,
"linux-arch@vger.kernel.org"@cisco.comlinux-arch@vger.kernel.org,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
maint_arch@dvomlehn-lnx2.corp.sa.net
Subject: Re: [PATCH 1/23] Make register values available to panic notifiers
Date: Mon, 12 Apr 2010 13:27:45 +0100 [thread overview]
Message-ID: <20100412122745.GC28208@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20100412060609.GA25273@dvomlehn-lnx2.corp.sa.net>
On Sun, Apr 11, 2010 at 11:06:09PM -0700, David VomLehn wrote:
> This patch makes panic() and die() registers available to, for example,
> panic notifier functions. Panic notifier functions are quite useful
> for recording crash information, but they don't get passed the register
> values. This makes it hard to print register contents, do stack
> backtraces, etc. The changes in this patch save the register state when
> panic() is called and introduce a function for die() to call that allows
> it to pass in the registers it was passed.
Can you explain why you want this?
I'm wondering about the value of saving the registers; normally when a panic
occurs, it's because of a well defined reason, and not because something
went wrong in some CPU register; to put it another way, a panic() is a
more controlled exception than a BUG() or a bad pointer dereference.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
WARNING: multiple messages have this Message-ID (diff)
From: Russell King <rmk@arm.linux.org.uk>
To: David VomLehn <dvomlehn@cisco.com>
Cc: to@dvomlehn-lnx2.corp.sa.net,
"linux-arch@vger.kernel.org"@cisco.com,
linux-arch@vger.kernel.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org,
maint_arch@dvomlehn-lnx2.corp.sa.net
Subject: Re: [PATCH 1/23] Make register values available to panic notifiers
Date: Mon, 12 Apr 2010 13:27:45 +0100 [thread overview]
Message-ID: <20100412122745.GC28208@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20100412060609.GA25273@dvomlehn-lnx2.corp.sa.net>
On Sun, Apr 11, 2010 at 11:06:09PM -0700, David VomLehn wrote:
> This patch makes panic() and die() registers available to, for example,
> panic notifier functions. Panic notifier functions are quite useful
> for recording crash information, but they don't get passed the register
> values. This makes it hard to print register contents, do stack
> backtraces, etc. The changes in this patch save the register state when
> panic() is called and introduce a function for die() to call that allows
> it to pass in the registers it was passed.
Can you explain why you want this?
I'm wondering about the value of saving the registers; normally when a panic
occurs, it's because of a well defined reason, and not because something
went wrong in some CPU register; to put it another way, a panic() is a
more controlled exception than a BUG() or a bad pointer dereference.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2010-04-12 12:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 6:06 [PATCH 1/23] Make register values available to panic notifiers David VomLehn
2010-04-12 6:06 ` David VomLehn
2010-04-12 6:24 ` Mike Frysinger
2010-04-12 6:24 ` Mike Frysinger
2010-04-12 11:16 ` David Howells
2010-04-12 11:16 ` David Howells
2010-04-14 20:41 ` David VomLehn
2010-04-14 23:52 ` David Howells
2010-04-14 23:58 ` David Miller
2010-04-14 20:42 ` David VomLehn
2010-04-12 12:03 ` Heiko Carstens
2010-04-12 12:03 ` Heiko Carstens
2010-04-12 12:20 ` David Howells
2010-04-12 12:20 ` David Howells
2010-04-12 12:24 ` Russell King
2010-04-12 12:24 ` Russell King
2010-04-14 20:47 ` David VomLehn
2010-04-12 12:27 ` Russell King [this message]
2010-04-12 12:27 ` Russell King
2010-04-12 12:45 ` David Howells
2010-04-14 21:04 ` David VomLehn
2010-04-12 13:35 ` Martin Schwidefsky
2010-04-12 13:35 ` Martin Schwidefsky
2010-04-14 21:09 ` David VomLehn
2010-04-14 21:00 ` David VomLehn
2010-04-15 2:54 ` Paul Mundt
-- strict thread matches above, loose matches on Subject: below --
2010-04-12 6:03 David VomLehn
2010-04-12 21:57 ` Andrew Morton
2010-04-14 22:02 ` David VomLehn
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=20100412122745.GC28208@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc="linux-arch@vger.kernel.org"@cisco.comlinux-arch \
--cc=dvomlehn@cisco.com \
--cc=to@dvomlehn-lnx2.corp.sa.net \
/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.