From: Peter Zijlstra <peterz@infradead.org>
To: Hui Zhu <teawater@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Marc Khouzam <marc.khouzam@ericsson.com>,
Thiago Jung Bauermann <thiago.bauermann@gmail.com>,
Steven <mqyoung@gmail.com>,
colyli@gmail.com, Christoph Hellwig <hch@infradead.org>,
Jason Wessel <jason.wessel@windriver.com>
Subject: Re: KGTP (Linux Kernel debugger and tracer) 20110405 release
Date: Wed, 06 Apr 2011 10:19:19 +0200 [thread overview]
Message-ID: <1302077959.2225.1378.camel@twins> (raw)
In-Reply-To: <BANLkTinU5s8FgC9acCPcQqDRBnwi4EqA2g@mail.gmail.com>
On Wed, 2011-04-06 at 13:54 +0800, Hui Zhu wrote:
> This is a good question.
>
> The KGTP is completely different with KGDB. It will not supply simple
> gdbrsp debug interface to user. It just supply interface between the
> kernel tracepoint(Now, just support kprobe, will add others later) and
> GDB tracepoint function.
>
> So user can debug and trace Linux kernel with GDB without stop the
> Linux Kernel (So the GDB can running on this Kernel). It is a trace
> tools and debug tools.
But this isn't really an answer either. Could you extend the existing
KGDB infrastructure to provide these features and thereby re-use
existing infrastructure to reduce your patch size and code duplication?
Jason (the KGDB maintainer) certainly thought there was much possibility
there when I spoke to him yesterday.
Think of it this way, wouldn't it be much better if there was one tool
that could provide the combined feature set of KGDB and KGTP?
next prev parent reply other threads:[~2011-04-06 8:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 11:59 KGTP (Linux Kernel debugger and tracer) 20110405 release Hui Zhu
2011-04-05 14:21 ` Harry Wei
2011-04-05 17:27 ` Peter Zijlstra
2011-04-06 5:54 ` Hui Zhu
2011-04-06 8:19 ` Peter Zijlstra [this message]
2011-04-08 5:36 ` Hui Zhu
2011-04-08 6:41 ` Dongdong Deng
2011-04-08 7:58 ` Hui Zhu
2011-04-08 8:25 ` Hui Zhu
2011-04-21 2:46 ` Steven Rostedt
2011-04-21 3:27 ` Hui Zhu
2011-04-06 13:44 ` Dominique Toupin
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=1302077959.2225.1378.camel@twins \
--to=peterz@infradead.org \
--cc=colyli@gmail.com \
--cc=hch@infradead.org \
--cc=jason.wessel@windriver.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.khouzam@ericsson.com \
--cc=mqyoung@gmail.com \
--cc=teawater@gmail.com \
--cc=thiago.bauermann@gmail.com \
/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