From: Ingo Molnar <mingo@elte.hu>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Jason Wessel <jason.wessel@windriver.com>,
lkml <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: kgdboe?
Date: Tue, 6 May 2008 15:16:32 +0200 [thread overview]
Message-ID: <20080506131632.GD2146@elte.hu> (raw)
In-Reply-To: <200805051110.32238.jbarnes@virtuousgeek.org>
* Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> So when will we see kgdboe or some other way of getting gdb to connect
> to the target over ethernet upstream?
i think the proper way would be to extend the kgdb-over-console (kgdboc)
concept and make it easy to utilize the existing netconsole code via
KGDB. This brings nice synergy: netconsole is utilized by other debug
infrastructure as well so anything that supports netconsole would
automatically support KGDB as well. I dont really like the old kgdboe
approach from a design POV as it created a parallel infrastructure for
special-purpose kgdb IO.
likewise, the firewire debugging code could/should be extended to create
a bidirectional console as well - that has other benefits as well. (we'd
get printks over firewire - instead of the special-purpose firescope
utility)
and the early console drivers could be reused to do early debugging via
KGDB as well.
Ingo
next prev parent reply other threads:[~2008-05-06 13:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 12:32 [GIT PULL] kgdb fixes for 2.6.26 Jason Wessel
2008-05-05 18:10 ` kgdboe? Jesse Barnes
2008-05-06 13:16 ` Ingo Molnar [this message]
2008-05-06 17:05 ` kgdboe? Jesse Barnes
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=20080506131632.GD2146@elte.hu \
--to=mingo@elte.hu \
--cc=davem@davemloft.net \
--cc=hch@infradead.org \
--cc=jason.wessel@windriver.com \
--cc=jbarnes@virtuousgeek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.