[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200704172045.03743.ak@suse.de>
Date: Tue, 17 Apr 2007 20:45:03 +0200
From: Andi Kleen <ak@...e.de>
To: Randy Dunlap <randy.dunlap@...cle.com>
Cc: piet@...elane.com, Tom Rini <trini@...nel.crashing.org>,
Dave Jiang <djiang@...sta.com>, linux-kernel@...r.kernel.org,
sshtylyov@...mvista.com, Andrew Morton <akpm@...l.org>,
George Anzinger <george@...dturkeyranch.net>,
"David O'Brien" <obrien@...ebsd.org>
Subject: Re: Permanent Kgdb integration into the kernel - lets get with it.
> Is there any movement on this?
I'm open to reasonable patches for the hooks at least. If that is done
then the actual kgdb code can be reviewed and considered eventually too.
But just having the hooks in would make it easy enough to use anyways
(no patching, just dropping in of new files, or even loading of it as a
module into any kernel)
When I did the original x86-64 kgdb port this worked nicely --
kgdb could work with just the standard die notifiers and a simple
change in the serial console code.
The recent kgdb seems to need much more changes again though.
However every time when I suggested this (fixing the hooks first
and submitting the really needed changes piece by piece)
there didn't seem to be any interest from the various kgdb maintainers.
So my impression currently is that they're not interested in merging.
Another problem is that kgdb is moving more and more away from
mainline by adding various weird hacks and workarounds in random
code that just make merging harder.
Before anything could be considered for merging that all would
need to be cleaned up.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists