From: Tom Rini <trini@kernel.crashing.org>
To: George Anzinger <george@mvista.com>
Cc: Andrew Morton <akpm@osdl.org>,
dhowells@redhat.com, torvalds@osdl.org, davidm@snapgear.com,
linux-kernel@vger.kernel.org, uclinux-dev@uclinux.org
Subject: Re: [PATCH] Additional kgdb hooks
Date: Fri, 19 Nov 2004 15:06:47 -0700 [thread overview]
Message-ID: <20041119220647.GK16043@smtp.west.cox.net> (raw)
In-Reply-To: <419152D8.9030303@mvista.com>
On Tue, Nov 09, 2004 at 03:29:28PM -0800, George Anzinger wrote:
> Andrew Morton wrote:
> >dhowells@redhat.com wrote:
> >
> >>The attached patch adds a couple of extra hooks by which kgdb or an
> >>equivalent
> >>gdbstub can catch bad_page() and panic() invocations.
> >
> >
> >Tom is valiantly flogging his way through a generic KGDB implementation. I
> >think it would be better to push ahead with that and to not put into
> >generic code hooks which are specific to one arch's kgdb implementation.
>
> IMNSHO the trap should be in dump_stack(). That way it catches a bunch of
> things all at once.
The hard question is how to do this cleanly. Perhaps changing things
slightly so that lib/dump_stack.c provides the 'true' dump_stack() (or
moving it to kernel/dump_stack.c) which calls a notify chain and then
arch_dump_stack() ?
> Also, panic has a notify option that kgdb should use just like everybody
> else.
This is a good idea, I'm surprised we didn't already do, so I've just
done it.
--
Tom Rini
http://gate.crashing.org/~trini/
prev parent reply other threads:[~2004-11-19 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-08 14:32 dhowells
2004-11-08 16:41 ` Tom Rini
2004-11-08 16:55 ` David Howells
2004-11-08 22:44 ` Andrew Morton
2004-11-09 23:29 ` George Anzinger
2004-11-19 22:06 ` Tom Rini [this message]
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=20041119220647.GK16043@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=davidm@snapgear.com \
--cc=dhowells@redhat.com \
--cc=george@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=uclinux-dev@uclinux.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
Powered by JetHome