From: Tom Rini <trini@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Tom Rini <trini@kernel.crashing.org>, lkml <linux-kernel@vger.kernel.org>
Message-Id: <20051110163906.20950.45704.sendpatchset@localhost.localdomain>
Subject: [PATCH,RFC 2.6.14 00/15] KGDB Support
Date: Thu, 10 Nov 2005 11:38:40 -0500
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1997
Lines: 39

[ Using a different script that doesn't do individual patch CC's, but should
  send to lkml this time ]

I'm once again submitting the KGDB found at
http://sourceforge.net/projects/kgdb for inclusion in the kernel.  Right now,
I'm mainly asking for comments again.  This series is against 2.6.14, and that
means it will fail, probably voilently, against 2.6.15-rc1 when it comes out
due to the PowerPC merge (aside, Paul, I'll take care of merging the old kgdb
;)), but I'd still like to get this into Andrew's tree at somepoint during
2.6.15 for future inclusion in Linus' tree, and will take back up tracking the
-rc releases at least.

This version of KGDB is designed so that as much code as possible is done in
a core file shared by all architectures, and with I/O (ie
8250 serial, custom uart, ethernet) being common when possible and modular.
The rough splitup of this is that 95% of the interaction with KGDB is done in
files common to all implementations with a small set of architecture specific
things (setjmp/longjmp, actually formatting registers for GDB, single
stepping).

Much of how to use this version (it is slightly different from George
Anzinger's version) is written up in DocBook and viewable that way.  I've
tried to do this in as clean a way as possible (notifier when possible for
example) so that it's as minimally instrusive as possible.  But, in order to
allow for KGDB to be used very early on (some folks argue this is critical,
some argue it's not) there's a few hooks so we can know if pidhash_init has
been run, or to try and have KGDB break in as soon as possible, if it can't
right then (such as on x86_64 where we're still trying to deal with early
per-cpu things so we can work early).

Comments?  Thanks!

-- 
Tom
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/