Re: 2.6.23-rc1-mm2

[Paul Mundt]

On Wed, Aug 01, 2007 at 03:58:48AM -0400, Mike Frysinger wrote:
> On 8/1/07, Paul Mundt <lethal@xxxxxxxxxxxx> wrote:
> > On Tue, Jul 31, 2007 at 11:09:32PM -0700, Andrew Morton wrote:
> > > - Is anyone testing the kgdb code in here?
> >
> > Testing, yes. Succeeding, no. It's utterly hosed on SH in its present
> > condition at least. Presumably it's been tested on at least one platform
> > with some measure of success, but it's certainly not mine ;-)
> 
> does kgdb actually have a chance to get merged ?  with the history of
> it, i just assumed it was never going in, so we've been using our own
> kgdb patch on Blackfin ... so the version *we have* works great :) but
> if there's a chance of this actually going mainline, we can see about
> testing that version as well ...

The generic code has a better chance of being merged if it actually works
at least and doesn't break every platform out there that has an existing
stub. It offers quite a bit of new functionality and does clean things up
a bit, so it would certainly be nice to get things to use that, rather
than having to duplicate all of this crap in the architectures. If it's
not going to be merged, everyone will of course continue using the
existing in-tree stubs (sh, ppc, etc.).

It's generally advantageous to get these things working on your
architecture _before_ things are merged however, as it's one less thing
to catch up on after the fact. It also helps to figure out if there are
issues with the current implementation by trying it out on your platform
in advance, it's a lot more work to push back against it once it's
already merged.

The fact that no one has bothered to even compile for the platforms the
generic kgdb stuff is ported to does seem to suggest that the kgdb folks
aren't terribly serious about getting it merged, though.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/