From: fche@redhat.com (Frank Ch. Eigler)
To: Jovi Zhang <bookjovi@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] ktap: Another dynamic tracing tool for Linux
Date: Mon, 31 Dec 2012 13:58:39 -0500 [thread overview]
Message-ID: <y0mliceujz4.fsf@fche.csb> (raw)
In-Reply-To: <CACV3sb+69VQMM44vXx_-AdOZmbz18zZeVdmi1+YHEq7kZ_VmdA@mail.gmail.com> (Jovi Zhang's message of "Mon, 31 Dec 2012 11:32:39 +0800")
bookjovi wrote:
> [...] This mail is RFC for discuss on a new dynamic tracing tool, I
> name it ktap. (only experimental project now)
Welcome to the problem domain!
> [...]
> what ktap differentiates with Systemtap is:
> [...]
> 2). ktap have good portability, because it compile source file to
> bytecode, like python and Java.
(From this PoV, systemtap is just as portable as the kernel, as it
generates the same sort of C code the kernel is built from.)
> [...]
> 5). ktap will be open source completely, with GPL license, it might be
> merge into mainline in someday, that's very convince for tracing user.
(systemtap has always been GPLv2, ever since its beginning in 2005.)
> [...]
> ktap use lua language syntax and bytecode as initial implementation,
Interesting approach. I recall we considered it way back when, but
rejected it for a couple of reasons, including the at-the-time
perceived unwelcomeness of a serious bytecode interpreter within the
kernel.
> it could support kprobe, uprobe, userspace probe, etc.
Great.
> I wish you can give me some technical architecture pre-review for
> ktap, before ktap release 1.0.
> Any comments is welcome, thanks very much.
Have you made any source code available yet?
- FChE
next prev parent reply other threads:[~2012-12-31 18:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 3:32 [RFC] ktap: Another dynamic tracing tool for Linux Jovi Zhang
2012-12-31 18:58 ` Frank Ch. Eigler [this message]
2013-01-04 8:13 ` Jovi Zhang
2013-01-04 15:19 ` Frank Ch. Eigler
2013-01-18 1:24 ` Jovi Zhang
2013-01-18 3:35 ` Frank Ch. Eigler
2013-01-18 4:02 ` Jovi Zhang
[not found] <917750116.79371357913957820.JavaMail.root@srv11.zimbra.polymtl.ca>
[not found] ` <422821122.79411357913979039.JavaMail.root@srv11.zimbra.polymtl.ca>
2013-01-13 3:50 ` Jovi Zhang
[not found] <68461756.264831358192004350.JavaMail.root@srv11.zimbra.polymtl.ca>
2013-01-14 19:39 ` Michel Dagenais
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=y0mliceujz4.fsf@fche.csb \
--to=fche@redhat.com \
--cc=bookjovi@gmail.com \
--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