From: Yumiko Sugita <sugita@sdl.hitachi.co.jp>
To: linux-kernel@vger.kernel.org
Cc: lkst-develop@lists.sourceforge.net
Subject: Release of LKST 1.0
Date: Mon, 15 Apr 2002 19:21:51 +0900 [thread overview]
Message-ID: <5.0.2.6.2.20020415191635.00c5aeb0@sdl99c> (raw)
Dear all,
I'd like to announce publication of Linux Kernel State Tracer (LKST) 1.0,
which is a tracer for Linux kernel.
LKST's main purpose is debugging, fault analysis and performance analysis of
enterprise systems.
For the purpose, LKST has these features,
- It is possible to change dynamically which events are recorded.
Developers can obtain information about the events which they
concern only interesting events.
And, It reduces the overhead of components which is not related
with trouble.
- It is possible to change each function invoked each events.
A default function of all events is just recording the events.
But, if it is necessary, default function can be changed to
another function.
For example, this feature can be used as following:
+ Notify user processes when the function detects abnormal status.
+ Change a maskset,which controls what type of events should be
recorded, dynamically by the function.
-> The system can usually run with a few events trace for the
cause of good performance. And, when the function detects
abnormal status, it can change a maskset to get more
detail information.
Users can create and install any function as kernel module.
We released the beta version of LKST in January, 2002. And the followings are
added with the LKST 1.0.
- Replace the current trace hooks with Kernel Hooks (formerly known as GKHI)
by IBM.
- Integrate with Linux Kernel Crash Dump (LKCD) to analyze the trace data
in a crash dump.
- Making of daemon that saves trace data into log files.
Note: The LKCD patch is not a official patch. If the official patch is released,
we will replace it with the official patch and release the LKST again.
LKST binaries, source code and documents are available in the following site,
https://sourceforge.net/projects/lkst/
or
http://oss.hitachi.co.jp/sdl/english/lkst.html (now updating)
We prepared a mailing list written below in order to let users know
update of LKST.
lkst-users@lists.sourceforge.net
To subscribe, please refer following URL,
http://lists.sourceforge.net/lists/listinfo/lkst-users
And if you have any comments, please send to the above list, or to
another mailing
list written below.
lkst-develop@lists.sourceforge.net
With kindest regards,
All of the LKST developers
----------------
Yumiko Sugita
Hitachi,Ltd., Systems Development Laboratory
reply other threads:[~2002-04-15 10:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5.0.2.6.2.20020415191635.00c5aeb0@sdl99c \
--to=sugita@sdl.hitachi.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=lkst-develop@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®