public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Hui Zhu <teawater@gmail.com>
Cc: Dongdong Deng <libfetion@gmail.com>,
	Jason Wessel <jason.wessel@windriver.com>,
	Peter Zijlstra <peterz@infradead.org>,
	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>
Subject: Re: KGTP (Linux Kernel debugger and tracer) 20110405 release
Date: Wed, 20 Apr 2011 22:46:49 -0400	[thread overview]
Message-ID: <20110421024648.GA24898@home.goodmis.org> (raw)
In-Reply-To: <BANLkTi=BQVjXRLNxiCU0xaYrDShtRgiC6Q@mail.gmail.com>

On Fri, Apr 08, 2011 at 04:25:28PM +0800, Hui Zhu wrote:
> After a discussion with Dongdong, I think I have different idea with that.
> 
> 1. I don't want change the current interface of kgtp.  Because a proc
> interface is very simple and stable interface.
> And with proc, kgtp can very easy connect with GDB without Kernel

Can you use the debugfs interface instead of proc. Proc is too
overloaded as is, and debugfs seems to be a perfect match in this case.

-- Steve

> help.  Please see
> https://code.google.com/p/kgtp/wiki/HOWTO#Make_GDB_connect_to_gtp and
> https://code.google.com/p/kgtp/wiki/HOWTO#Offline_debug
> 
> 2. I don't want remove the kprobe.  Because what I want kgtp is to be
> a Linux Kernel tracepoint interface with gdb.  I will add other
> tracepoint like TRACE_EVENT.
> And move it to gdb breakpoint is too far away from it.  And it is too
> much depend on kgdb.
> 
> Of course, I am very happy to share the GDB rsp tracepoint parse code
> with kgdb to make it support gdb tracepoint.
> Trust me, My code is more clear than the doc of GDB.  :)
> 

  reply	other threads:[~2011-04-21  2:46 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
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 [this message]
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=20110421024648.GA24898@home.goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=colyli@gmail.com \
    --cc=hch@infradead.org \
    --cc=jason.wessel@windriver.com \
    --cc=libfetion@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.khouzam@ericsson.com \
    --cc=mqyoung@gmail.com \
    --cc=peterz@infradead.org \
    --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