Re: [KGDB PATCH][7/7] Move debugger_entry()

[Tom Rini <trini@kernel.crashing.org>]

On Thu, Mar 11, 2004 at 02:49:16PM -0800, George Anzinger wrote:

> Tom Rini wrote:
[snip]
> >For kgdboe, you need to wait for the ethernet driver, networking, etc.
> >Without going and trying to do some big special case, that's when it has
> >to be, for kgdboe.
> >
> >For serial, esp if you make kgdb_arch_init() handle kgdb_serial pointer,
> >it can happen much earlier.  In fact, in that case you could probably
> >throw breakpoint() in as first line of C (PPC32) or close to it (some
> >mappings needed i386, sh, others, generally speaking).
> 
> So the question is do we cater to the worst or the best?  If I put kgdb or 
> what ever on the command line, I would like to see the connection ASAP what 
> ever the connection is.  So possibly, the command line parse part of kgdb 
> sets a flag it it can not do the break NOW.  The late bloomer code finds 
> this flag when doing the kgdboe or what ever set up and enters at that 
> time.  Puts a little more smarts in the command line part, but gets things 
> rolling ASAP regardless of the interface.  This, of course, assumes that 
> the kgdboe or what ever has an independent way of getting entered as soon 
> as it can be set up, i.e. its prerequisites are satisfied.

This sound like what I passed along from dwmw2 a week ago I think. :)

-- 
Tom Rini
http://gate.crashing.org/~trini/