From: Geunsik Lim <leemgs1@gmail.com>
To: Hui Zhu <teawater@gmail.com>
Cc: linux-kernel@vger.kernel.org,
"gdb@sourceware.org" <gdb@sourceware.org>,
kgtp <kgtp@freelists.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>,
Steven Rostedt <rostedt@goodmis.org>,
Randy Dunlap <rdunlap@xenotime.net>
Subject: Re: KGTP (Linux Kernel debugger and tracer) 20111218 release
Date: Wed, 04 Jan 2012 15:48:00 -0000 [thread overview]
Message-ID: <CABiHV1QoPf1KK-BqRv7GMmVabKJm9GEz5kyN63nX0ASXsaF7eA@mail.gmail.com> (raw)
In-Reply-To: <CANFwon0=VMXuXKDqZVYxad42J8hJ6wSuiPE4Sr0cSaxSo6dMPQ@mail.gmail.com>
On Thu, Jan 5, 2012 at 12:12 AM, Hui Zhu <teawater@gmail.com> wrote:
> On Mon, Dec 26, 2011 at 15:53, Geunsik Lim <leemgs1@gmail.com> wrote:
>> On Fri, Dec 23, 2011 at 3:21 PM, Hui Zhu <teawater@gmail.com> wrote:
>>> Hi Geunsik,
>>>
>>> On Fri, Dec 23, 2011 at 12:58, Geunsik Lim <leemgs1@gmail.com> wrote:
>>>> On Sun, Dec 18, 2011 at 9:11 PM, Hui Zhu <teawater@gmail.com> wrote:
>>>>> KGTP is a realtime and lightweight Linux Kernel debugger and tracer.
>>>>>
>>>>> It makes Linux Kernel supply a GDB remote debug interface. Then GDB in
>>>>> current machine or remote machine (see
>>>>> https://code.google.com/p/kgtp/wiki/HOWTO#Make_GDB_connect_to_gtp) can
>>>>> debug and trace Linux through GDB tracepoint without stopping the
>>>>> Linux Kernel.
>>>>> And even if the board doesn't have GDB on it and doesn't have
>>>>> interface for remote debug. It can debug the Linux Kernel using
>>>>> offline debug (See
>>>>> https://code.google.com/p/kgtp/wiki/HOWTO#Offline_debug).
>>>>> And it can work with Android (See
>>>>> https://code.google.com/p/kgtp/wiki/HowToUseKGTPinAndroid).
>>>>> Now, it supports X86-32, X86-64, MIPS and ARM.
>>>>>
>>>>> Now, KGTP 20111218 release.
>>>>> You can get the package for it from
>>>>> http://kgtp.googlecode.com/files/kgtp_20111218.tar.bz2
>>>>> or
>>>>> svn co https://kgtp.googlecode.com/svn/tags/20111218
>>>>>
>>>>> The change of this release is:
>>>>> Add gtp_rb to be the new frame buffer to make trace record speed up
>>>>> and more friendly to the older version Linux kernel.
>>>>> Rename gtp.patch to gtp_for_review.patch.
>>>>> Add Linux Kernel patch gtp_3.0_to_upstream.patch(3.0 to upstream),
>>>>> gtp_2.6.39.patch(2.6.39), gtp_2.6.33_to_2.6.38.patch(2.6.33 to 2.6.38)
>>>>> and gtp_older_to_2.6.32.patch(older to 2.6.32).
>>>> Thank you for your upgrade work for the compatibility among various
>>>> linux version.
>>>> I am testing normally on evaluation board based on ARM cortex using
>>>> the latest Linux.
>>>
>>> Thanks. Please tell me if you get some trouble with it.
>>>
>>>>> Then you can include KGTP in your Kernel source tree.
>>>>> Add special trace state variable $gtp_version to show the version of KGTP.
>>>>> Fix some build errors of gtp_for_review.patch.
>>>>> Fix some build errors in ARM.
>>>>> Update doc.
>>>>> To get other change info please goto https://code.google.com/p/kgtp/wiki/UPDATE
>>>>>
>>>>> According to the comments of Christoph. I make a patch for Linux
>>>>> Kernel and make it looks OK with checkpatch.pl. The file
>>>>> gtp_for_review.patch is include in the source of KGTP code.
>>>> I have one question about KGTP.
>>>> Previously, GDB Tracepoints for linux Linux kernel 2.6.19 is developed
>>>> by Jim Blandy
>>>> of Cygnus. He also presented to share this practical approach at FOSDEM 2007.
>>>> If you can, Can you explain the difference(e.g: merits, demerits, and
>>>> so on) between
>>>> GDB Tracepoint of Jim and KGTP by you?
>>>
>>> I am not sure about this one. Because I cannot find anything about
>>> it. Could you give me a link or something?
>> Sorry I am late because of X-mas day.
>> Refer to http://www.red-bean.com/trac/tracepoints
>> You can read about Tracepoints for the Linux kernel in detail at the
>> above website .
>
> Is it included in Kernel upstream?
Currently, GDB Tracepoint of Jim is not included in mainline version.
> It is not update for a long time.
My questions is not the merging issue into latest Linux (upstream kernel).
I want you to explain the merits of KGTP compared to GDB Tracepoint
of Jim that presented
at FOSDEM 2007.
When I compared/checked internals between KGTP and GDB Tracepoint of
Jim, It seems
that both are same approaches. Can you share the difference(e.g:
merits, demerits, design,
and so on) between GDB Tracepoint of Jim and KGTP of you If you can?
Thanks.
>
>
>>>
>>> For now, I just know the difference is I am a GDB developer too. So I
>>> can make KGTP develop more close to GDB devekop. It can handle some
>>> issue more easy.
>>>
>>> Thanks,
>>> Hui
>>>
>>>>
>>>>>
>>>>> Thanks,
>>>>> Hui
>>>>
>>>>
>>>>
>>>> --
>>>> Best regards,
>>>> Geunsik Lim ( Samsung Electronics )
>>>> Blog : http://blog.naver.com/invain/
>>>> Homepage: http://leemgs.fedorapeople.org
>>>> --
>>>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>>>> the body of a message to majordomo@vger.kernel.org
>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>>> Please read the FAQ at http://www.tux.org/lkml/
>>
>>
>>
>> --
>> Best regards,
>> Geunsik Lim ( Samsung Electronics )
>> Blog : http://blog.naver.com/invain/
>> Homepage: http://leemgs.fedorapeople.org
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
--
Best regards,
Geunsik Lim, Samsung Electronics
Homepage: http://leemgs.fedorapeople.org
-----------------------------------------------------------------------
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
-----------------------------------------------------------------------
prev parent reply other threads:[~2012-01-04 15:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-18 12:12 Hui Zhu
2011-12-23 4:58 ` Geunsik Lim
2011-12-23 6:22 ` Hui Zhu
2011-12-26 7:54 ` Geunsik Lim
2012-01-04 15:13 ` Hui Zhu
2012-01-04 15:48 ` Geunsik Lim [this message]
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=CABiHV1QoPf1KK-BqRv7GMmVabKJm9GEz5kyN63nX0ASXsaF7eA@mail.gmail.com \
--to=leemgs1@gmail.com \
--cc=colyli@gmail.com \
--cc=gdb@sourceware.org \
--cc=hch@infradead.org \
--cc=kgtp@freelists.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.khouzam@ericsson.com \
--cc=mqyoung@gmail.com \
--cc=rdunlap@xenotime.net \
--cc=rostedt@goodmis.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).