From: George Anzinger <george@mvista.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Tom Rini <trini@kernel.crashing.org>,
pavel@ucw.cz, linux-kernel@vger.kernel.org
Subject: Re: kgdb support in vanilla 2.6.2
Date: Thu, 19 Feb 2004 16:15:29 -0800 [thread overview]
Message-ID: <403551A1.7070208@mvista.com> (raw)
In-Reply-To: <20040204161626.1a2f8885.akpm@osdl.org>
Andrew Morton wrote:
> Tom Rini <trini@kernel.crashing.org> wrote:
>
>>Andrew, what features of George's version don't you like?
>
>
> This is bad:
>
> akpm:/usr/src/25> grep '^+#ifdef' patches/kgdb-ga.patch | wc -l
> 83
>
> and the fact that it touches 36 different files.
Been away from this for a while, but I do think this needs a comment. The fact
that it touches 36 files is tilted rather strongly in that a good number of
those files are in the Document/* tree. I.e. there is a rather larger amount of
documentation.
As to the #ifdefs, I once worked on a kernel (HPUX if you must know) where you
could NOT remove the debug stub and its bits. Turns out the kernel began to
depend on the code that was supposed to be debugging it. I rather strongly try
to avoid Heisenberg and the nasty thinks that arise from this sort of thing. I
think you will find that most of those #ifdefs are "#ifdef CONFIG_KGDB" so that
it you turn it off it is just as if the patch was not done (save the configure
script, of course).
There is also the attempt to make one patch cover several kernels (such as in
the 2.4 case where we may have O(1) or not) and also the preempt or not AND at
the same time, want to debug the preempt code.
>
> Any time I've had to do any maintenance work against that stub I get lost
> in a twisty maze and just whine at George about it. It's just all over the
> place. Yes, this is partly the nature of the beast, but I don't see that a
> ton of effort has been put into reducing the straggliness.
Yes, I agree. Some of this is caused by the need to work with a rather fixed
interface to gdb. We would, for example, like to tell gdb to flush its cache
from time to time. It would also be nice if gdb were to hint to us about what
it was trying to do. The single step over a break point comes to mind here, as
does the function call set up. Still, improvements can be made.
>
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
next prev parent reply other threads:[~2004-02-21 0:02 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 23:01 kgdb support in vanilla 2.6.2 Pavel Machek
2004-02-04 23:21 ` Andrew Morton
2004-02-04 23:24 ` Pavel Machek
2004-02-04 23:45 ` Andrew Morton
2004-02-04 23:55 ` Tom Rini
2004-02-05 0:16 ` Andrew Morton
2004-02-05 0:23 ` Tom Rini
2004-02-20 0:15 ` George Anzinger [this message]
2004-02-04 23:39 ` La Monte H.P. Yarroll
2004-02-04 23:54 ` Andrew Morton
2004-02-05 1:19 ` Pavel Machek
2004-02-20 0:24 ` George Anzinger
2004-02-05 0:39 ` Pavel Machek
2004-02-04 23:52 ` Tom Rini
2004-02-05 0:17 ` Paul Mundt
2004-02-05 0:32 ` Tom Rini
[not found] <20040204230133.GA8702@elf.ucw.cz.suse.lists.linux.kernel>
[not found] ` <20040204155452.4 9c1eba8.akpm@osdl.org.suse.lists.linux.kernel>
[not found] ` <20040204152137.500e8319.akpm@osdl.org.suse.lists.linux.kernel>
[not found] ` <402182B8.7030900@timesys.com.suse.lists.linux.kernel>
[not found] ` <20040204155452.49c1eba8.akpm@osdl.org.suse.lists.linux.kernel>
2004-02-05 3:11 ` Andi Kleen
2004-02-05 12:16 ` Pavel Machek
2004-02-05 17:50 ` Amit S. Kale
2004-02-06 2:20 ` Andi Kleen
2004-02-06 11:58 ` Amit S. Kale
2004-02-06 12:16 ` Andi Kleen
2004-02-06 13:05 ` Amit S. Kale
2004-02-06 13:24 ` Andi Kleen
2004-02-06 13:44 ` Amit S. Kale
2004-02-28 0:05 ` George Anzinger
2004-03-01 9:38 ` Amit S. Kale
2004-03-02 21:10 ` George Anzinger
2004-03-02 21:27 ` Andrew Morton
2004-03-02 23:52 ` George Anzinger
2004-03-03 5:08 ` Amit S. Kale
2004-03-03 16:06 ` Tom Rini
2004-03-04 0:42 ` George Anzinger
2004-03-03 10:05 ` Andi Kleen
2004-03-04 0:43 ` George Anzinger
2004-03-04 0:50 ` Andi Kleen
2004-03-04 5:06 ` Amit S. Kale
2004-03-04 5:18 ` Andrew Morton
2004-03-04 5:29 ` Amit S. Kale
2004-03-04 5:44 ` Andrew Morton
2004-03-04 20:54 ` George Anzinger
2004-03-04 21:03 ` Tom Rini
2004-03-04 23:15 ` George Anzinger
2004-03-04 13:01 ` Andi Kleen
2004-02-11 14:52 ` Amit S. Kale
2004-02-10 21:56 ` George Anzinger
2004-02-13 19:42 ` Andi Kleen
2004-02-12 1:34 ` George Anzinger
2004-02-12 8:33 ` Andi Kleen
2004-02-27 21:09 ` Piet Delaney
2004-02-27 21:58 ` George Anzinger
2004-02-27 23:33 ` Pavel Machek
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=403551A1.7070208@mvista.com \
--to=george@mvista.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=trini@kernel.crashing.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