From: Tom Rini <trini@kernel.crashing.org>
To: Paul Mackerras <paulus@samba.org>
Cc: Andrew Morton <akpm@osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH,RFC 2.6.14 11/15] KGDB: ppc64-specific changes
Date: Thu, 10 Nov 2005 18:13:03 -0700 [thread overview]
Message-ID: <20051111011303.GO3839@smtp.west.cox.net> (raw)
In-Reply-To: <17267.60410.120520.63951@cargo.ozlabs.ibm.com>
On Fri, Nov 11, 2005 at 11:55:22AM +1100, Paul Mackerras wrote:
> Tom Rini writes:
>
> > This adds basic KGDB support to ppc64, and support for kgdb8250 on the 'Maple'
> > board. All of this was done by Frank Rowand (who is on vacation right now,
> > but I'll try and answer for him). This should work on any ppc64 board via
> > kgdboe, so long as there is an eth driver that supports netpoll. At the
> > moment this is mutually exclusive with XMON. It is probably possible to allow
> > them to be chained, but that sounds dangerous to me. This is similar to
> > ppc32, but ppc32 does not explicitly test.
>
> We already have infrastructure to allow either xmon or kdb to be used,
> and in fact both can be built in and you can select at runtime which
> you prefer. See the __debugger stuff in system.h. You should just be
> able to hook kgdb into that same infrastructure. We're also planning
> to move to using the die_notify stuff for getting all the significant
> events to the debugger.
The notify_die stuff is wonderful. If I had a ppc64 board, I'd give
that a whirl myself. This does, unless there was something I missed,
tie into the existing debugger pointer stuff (thats similar but
different from ppc32). Assuming it hasn't started already, if I can
find time I might give it a wack on arch/powerpc, since I assume my
AlBook works (if not, I see my LongTrail might ;))
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2005-11-11 1:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 16:38 [PATCH,RFC 2.6.14 00/15] KGDB Support Tom Rini
2005-11-10 16:39 ` [PATCH,RFC 2.6.14 01/15] KGDB: core infrastructure Tom Rini
2005-11-10 16:39 ` [PATCH,RFC 2.6.14 03/15] KGDB: ppc32-specific changes Tom Rini
2005-11-10 16:39 ` [PATCH,RFC 2.6.14 02/15] KGDB: i386-specific changes Tom Rini
2005-11-10 16:40 ` [PATCH,RFC 2.6.14 04/15] KGDB: 8250-like UART driver Tom Rini
2005-11-10 16:41 ` [PATCH,RFC 2.6.14 06/15] KGDB: IA64-specific changes Tom Rini
2005-11-10 16:41 ` [PATCH,RFC 2.6.14 05/15] KGDB: MIPS-specific changes Tom Rini
2005-11-10 16:41 ` [PATCH,RFC 2.6.14 08/15] KGDB: x86_64-specific changes Tom Rini
2005-11-10 16:41 ` [PATCH,RFC 2.6.14 07/15] x86_64: Add a notifier hook to the "no context" part of do_page_fault Tom Rini
2005-11-10 16:42 ` [PATCH,RFC 2.6.14 09/15] KGDB: SuperH-specific changes Tom Rini
2005-11-10 16:42 ` [PATCH,RFC 2.6.14 10/15] KGDB: ARM-specific changes Tom Rini
2005-11-10 16:43 ` [PATCH,RFC 2.6.14 11/15] KGDB: ppc64-specific changes Tom Rini
2005-11-11 0:55 ` Paul Mackerras
2005-11-11 1:13 ` Tom Rini [this message]
2005-11-10 16:44 ` [PATCH,RFC 2.6.14 13/15] KGDB: CFI annotations for better unwinding Tom Rini
2005-11-10 16:44 ` [PATCH,RFC 2.6.14 12/15] KGDB: netpoll-based ethernet driver Tom Rini
2005-11-10 16:45 ` [PATCH,RFC 2.6.14 14/15] KGDB: Fix for 'lost' SysRq events Tom Rini
2005-11-10 16:45 ` [PATCH,RFC 2.6.14 15/15] KGDB: Better support for loaded modules Tom Rini
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=20051111011303.GO3839@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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