From: Eli Carter <eli.carter@inet.com>
To: Andrew Morton <akpm@digeo.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: 2.5.64-mm6
Date: Fri, 14 Mar 2003 16:01:58 -0600 [thread overview]
Message-ID: <3E725156.5000102@inet.com> (raw)
In-Reply-To: <20030314125354.409ca02a.akpm@digeo.com>
Andrew Morton wrote:
> Eli Carter <eli.carter@inet.com> wrote:
>
>>Andrew Morton wrote:
>>
>>>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.64/2.5.64-mm6/
>>
>>[snip]
>>
>>>kgdb.patch
>>
>>I'm interested in this patch in your tree.
>
>
> You're brave.
Heh. Insane might be more like it. ;)
> The kgdb patch is pretty nasty-looking code. I've managed to keep it working
> for every kernel since 2.4.0-test10 while avoiding actually looking at it.
> (I turn the monitor off when the patch needs fixing). Fed it through Lindent
> once.
>
> George Anzinger is maintaining another strain of the stub, and that mostly
> works OK and has improved features. But the diff is larger and I once had a
> couple of problems with it and need to spend more time testing it. It's up
> to date though.
If I can feed you changes to kgdb, would you be interested in taking
them? What was the last patch you shipped with George's version? Which
do you think would be the right place to start?
>>Would breaking the arch-independent parts out to linux/kernel/gdbstub.c
>>be a reasonable change or is that a dumb question? ;)
>
>
> That would be a fantastic thing to do. Note that there are already about ten
> kgdb stubs in the shipped kernel at present. If you can identify exactly
> which functions need to be provided by the architecture, pull that out into
> struct kgdb_operations, etc then it would make maintenance and addition of
> new support much easier.
I guess I'll go hunting. :)
> We might even end up with something we could submit for inclusion without
> first having to set up an itwasntmenobodysawmedoit@yahoo.com account.
"We"... I like that word. ;) If you can act as 'upstream' for my
changes and answer quick questions, I'll feed you patches. Some testing
of x86 would be wonderful too. (And while I'm at it, can I send you my
Christmas wishlist? ;) ) I have to warn you, I don't know how far I'll
get. But I'll give it a shot. My current concern is getting it working
under ARM, and there is a kgdb patch for 2.4 ARM I can draw from.
I'm thinking I'll try to wind up with 2 or 3 patches, kgdb.patch,
kgdb-arm.patch, and kgdb-ia32.patch. Maybe.
Are you feeling "brave"? 8)
Eli
--------------------. "If it ain't broke now,
Eli Carter \ it will be soon." -- crypto-gram
eli.carter(a)inet.com `-------------------------------------------------
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2003-03-14 22:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-13 11:26 2.5.64-mm6 Andrew Morton
2003-03-13 16:23 ` 2.5.64-mm6 Jeremy Fitzhardinge
2003-03-13 19:34 ` 2.5.64-mm6 Andrew Morton
2003-03-13 20:07 ` 2.5.64-mm6 Roger Larsson
2003-03-14 3:04 ` 2.5.64-mm6 Steven Cole
2003-03-14 3:28 ` 2.5.64-mm6 Andrew Morton
2003-03-14 3:46 ` 2.5.64-mm6 Shawn
2003-03-14 3:51 ` 2.5.64-mm6 Andrew Morton
2003-03-14 3:56 ` 2.5.64-mm6 Robert Love
2003-03-13 20:35 ` 2.5.64-mm6 Thomas Molina
2003-03-14 9:29 ` 2.5.64-mm6 Alexander Hoogerhuis
2003-03-14 11:55 ` 2.5.64-mm6 Andrew Morton
2003-03-15 8:38 ` 2.5.64-mm6 Alexander Hoogerhuis
2003-03-14 12:01 ` 2.5.64-mm6 Helge Hafting
2003-03-14 12:14 ` 2.5.64-mm6 Andrew Morton
2003-03-14 20:38 ` 2.5.64-mm6 Eli Carter
2003-03-14 20:53 ` 2.5.64-mm6 Andrew Morton
2003-03-14 22:01 ` Eli Carter [this message]
2003-03-14 22:21 ` 2.5.64-mm6 Andrew Morton
2003-03-13 13:42 2.5.64-mm6 Felipe Alfaro Solana
2003-03-13 21:49 2.5.64-mm6 Felipe Alfaro Solana
2003-03-14 0:23 ` 2.5.64-mm6 Thomas Molina
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=3E725156.5000102@inet.com \
--to=eli.carter@inet.com \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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