From: Yoav Etsion <etsman@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: RFC: klogger: kernel tracing and logging tool
Date: Wed, 22 Feb 2006 17:25:21 +0200 [thread overview]
Message-ID: <43FC8261.9000207@gmail.com> (raw)
Hi all,
This may look like a shameless plug, but it is intended as an RFC:
over the past few years I've developed a kernel logging tool called
Klogger: http://www.cs.huji.ac.il/~etsman/klogger
In some senses, it is similar to the LTT - Linux Trace Toolkit (and was
actually developed because LTT did not suit my needs).
However, Klogger is much more flexible. The two key points being:
1.
it offers extremely low logging overhead (better than LTT and Dtrace) by
auto-generating the logging code from user-specified config files.
2.
it allows new events to be defined, and more importantly shared among
subsystems' developers, thus allowing to understand module/subsystem
interactions without an all encompassing knowledge.
This feature can allow developers to design the performance logging
while designing the subsystem to be logged, allowing other
developers/researchers to get some insights without having to fully
understand a subsystem's code.
I am very interested in the community's opinion on this matter, so if
anyone is interested you can find the design document, a HOWTO and
patches against 2.6.14/2.6.9 on my website:
http://www.cs.huji.ac.il/~etsman/klogger
or
http://linux-klogger.sf.net
Currently, we use this tool at the the Hebrew University, but if there
is public interest I can work on it further so it adheres to kernel code
standards (the tool currently does obscene things like writing to disk
from kernel threads :-P --- it was written before relayfs was out there).
Thanks,
Yoav Etsion
next reply other threads:[~2006-02-22 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 15:25 Yoav Etsion [this message]
2006-02-22 16:21 ` RFC: klogger: kernel tracing and logging tool Steven Rostedt
2006-02-22 17:35 ` Static instrumentation, was " Frank Ch. Eigler
2006-02-22 21:00 ` Yoav Etsion
2006-02-23 15:17 ` Steven Rostedt
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=43FC8261.9000207@gmail.com \
--to=etsman@gmail.com \
--cc=etsman@cs.huji.ac.il \
--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;
as well as URLs for NNTP newsgroup(s).