From: "Amit S. Kale" <amitkale@emsyssoft.com>
To: Pavel Machek <pavel@suse.cz>, Andrew Morton <akpm@osdl.org>
Cc: Tom Rini <trini@kernel.crashing.org>,
linux-kernel@vger.kernel.org,
KGDB bugreports <kgdb-bugreport@lists.sourceforge.net>,
Andi Kleen <ak@suse.de>, George Anzinger <george@mvista.com>,
Jim Houston <jim.houston@ccur.com>,
Matt Mackall <mpm@selenic.com>
Subject: Re: [PATCH][0/6] A different KGDB stub
Date: Wed, 18 Feb 2004 10:26:29 +0530 [thread overview]
Message-ID: <200402181026.29813.amitkale@emsyssoft.com> (raw)
In-Reply-To: <20040217225241.GC666@elf.ucw.cz>
On Wednesday 18 Feb 2004 4:22 am, Pavel Machek wrote:
> Hi!
>
> > > The following is my next attempt at a different KGDB stub
> > > for your tree
> >
> > Is this the patch which everyone agrees on?
>
> It is based on Amit's version, so I think answer is "yes". I certainly
> like this one.
I don't agree. I did a few more cleanups after Andi expressed concerns over
globals kgdb_memerr and debugger_memerr_expected.
I liked Pavel's approach. Let's first get a minimal kgdb stub into mainline
kernel. Even this much is going to involve some effort. We can merge other
features later.
Let's create a cvs tree at kgdb.sourceforge.net for kgdb components to be
pushed int mainline kernel. This split is to keep current kgdb unaffected.
People who are already using it won't be affected.
May I suggest we breakup this task into following tasklets. I have expanded
item 1 because Pavel has something that's already close. The rest of the
items can be discussed in detail later. These need not be done in this order
except for first 2 whose sequence is fixed.
1. A minimal kgdb stub
core.patch:
kgdbstub.c full.
No changes to module.c
No changes for CONFIG_KGDB_THREAD
No changes to calling convention of do_IRQ (Needs to be done)
CONFIG_KGDB_CONSOLE removed
i386.patch
No changes for CONFIG_KGDB_THREAD
No manipulation of kernel stack before entry into do_IRQ
No non-source level CFI directives.
2. Minimal x86_64.patch
3. Patch to sync ppc kgdb with arch independent stub
4. Patch to sync other architecture kgdbs with arch independent stub on help
from maintainers of those architectures.
5. KGDB_CONSOLE patch
This is a must for embedded boards that have only one serial port
6. gdb automatic module loading
7. CONFIG_KGDB_THREAD patch
This may or may not be a separate config option. This patch will include
x86_64 support required to enable threads.
8. i386 thread support
9. Ethernet interface based on netconsole
10. ... Any other features
--
Amit Kale
EmSysSoft (http://www.emsyssoft.com)
KGDB: Linux Kernel Source Level Debugger (http://kgdb.sourceforge.net)
next prev parent reply other threads:[~2004-02-18 4:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 22:02 [PATCH][0/6] A different KGDB stub Tom Rini
2004-02-17 22:36 ` Andrew Morton
2004-02-17 22:52 ` Pavel Machek
2004-02-18 4:56 ` Amit S. Kale [this message]
2004-02-18 5:05 ` Andrew Morton
2004-02-18 12:56 ` Pavel Machek
2004-02-18 13:15 ` Amit S. Kale
2004-02-18 18:48 ` Pavel Machek
2004-02-18 18:21 ` Tom Rini
2004-02-19 4:46 ` Amit S. Kale
-- strict thread matches above, loose matches on Subject: below --
2004-02-12 0:02 Tom Rini
2004-02-12 0:27 ` Andrew Morton
2004-02-12 16:52 ` Tom Rini
2004-02-13 18:58 ` Chris Wright
2004-02-13 19:04 ` Tom Rini
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=200402181026.29813.amitkale@emsyssoft.com \
--to=amitkale@emsyssoft.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=george@mvista.com \
--cc=jim.houston@ccur.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=pavel@suse.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