mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH][0/6] A different KGDB stub
Date: Tue, 17 Feb 2004 15:02:36 -0700	[thread overview]
Message-ID: <20040217220236.GA16881@smtp.west.cox.net> (raw)

Hi Andrew.  The following is my next attempt at a different KGDB stub
for your tree (and then hopefully into kernel.org).  This is against
2.6.3-rc4 + bk-netdev-rc3 (from your tree), and nothing else.  This has
been tested on PPC32 (KGDB=y/n) and i386 (KGDB=y and allmodconfig) and
not at all on x86_64 (no time to build a toolchain yet).  Since the last
time, I've done the following:
- SysRq-G is always part of SYSRQ && KGDB.
- choice for I/O (8250 serial, kgdboe and PPC 'simple' serial, for now).
- On x86_64 / PPC32, we don't bother with CHK_DEBUGGER, but instead
  always use the arch provided debugger hooks.

Thre are 6 different patches:
core.patch: All of the non-arch specific bits, that aren't drivers.
8250.patch: The i/o driver for KGDB, via a standard PC uart.
kgdboe.patch: The i/o driver for KGDB, via netpoll.
i386.patch: The i386-specific code, tested.
ppc32.patch: The ppc32-specific code, tested.
x86_64.patch: The x86_64-specific bits, untested.

One last note.  For some reason, kgdboe isn't working for me right now.
But it doesn't look like it's something specific to the kgdboe driver
(Dropping in the -mm one and changing names to match still shows it, and
the serial driver is solid) so I'm not sure if it's anything other than
my bad luck today.  So if nothing else, if someone else could give this
a shot and let me know if it works for them...

-- 
Tom Rini
http://gate.crashing.org/~trini/

             reply	other threads:[~2004-02-17 22:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-17 22:02 Tom Rini [this message]
2004-02-17 22:36 ` Andrew Morton
2004-02-17 22:52   ` Pavel Machek
2004-02-18  4:56     ` Amit S. Kale
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=20040217220236.GA16881@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®