From sugita ＠ sdl.hitachi.co.jp Wed Sep 18 21:21:55 2002 From: sugita ＠ sdl.hitachi.co.jp (Yumiko Sugita) Date: Wed, 18 Sep 2002 21:21:55 +0900 Subject: [Lkst-develop] LKST v1.3リリースのお知らせ Message-ID: <5.0.2.6.2.20020918211152.0524f980@sdl99c> 各位 　Linux Kernel State Tracer (LKST) v1.3をリリースしましたのでお知らせ 致します。 　LKSTはデバッグおよび障害解析、性能解析を目的としたカーネル用イベント トレーサであり、下記の特徴を持っています。 （１）記録するイベントの動的な選択 ・その時点での目的にあった情報のみを採取することができ、障害に無関 　　係なイベント情報の採取によるオーバヘッドを削減できます。 （２）各イベントに対し、それを記録する関数の動的な変更 ・デフォルトでは多くのイベントに対し、イベント発生を記録する関数を割り 　　当てていますが、トレース中にこの関数を他の関数に変更できます。 　　・マスクセット(複数のイベントと各々に対する関数の定義)により一括して 　　切り替えることも可能です。これにより、平常時には最小限のトレースを 　　行ない、障害発生以降は関係するイベントの詳細情報の記録に切替える 　　などの運用が、容易に実現できます。 　　・これらの記録関数は、ユーザがカーネルの拡張モジュールとして組み 　　込むことも可能です。 （３）記録バッファの動的な作成・変更 　　・記録バッファを動的に作成し切替えることで、他のイベントの情報による 　　バッファの上書きを防ぎ、欲しい情報を残すことができます。 ――――――――――――――――――――― LKST のバイナリおよびソース、ドキュメントは下記の URL から入手できます。 https://sourceforge.net/projects/lkst/ http://sourceforge.jp/projects/lkst/ http://oss.hitachi.co.jp/sdl/english/lkst.html (現在更新中) 　なお、LKST v1.1がMiracle Linux v2.1に採用されています。Miracle Linux v2.1をお使いの方はパッチを当てることなくLKSTを使用できます。 ――――――――――――――――――――― LKST のアップデート等をお知らせするために、下記のML をご用意致して おります。 lkst-users ＠ lists.sourceforge.jp lkst-users ＠ lists.sourceforge.net 　本 ML のご購読には、下記 URL をご参照下さい。 http://lists.sourceforge.jp/mailman/listinfo/lkst-users http://lists.sourceforge.net/lists/listinfo/lkst-users 　コメント、バグレポートは、上記 ML か、開発者向けの下記ML までお願い 致します。 lkst-develop ＠ lists.sourceforge.jp lkst-develop ＠ lists.sourceforge.net LKST 開発チーム一同 *〜*〜*〜*〜*〜 Yumiko Sugita Hitachi, Ltd., Systems Development Laboratory Tel:+81-44-959-0258 Fax:+81-44-959-0855 　　　　　 〜*〜*〜*〜*〜* From sugita ＠ sdl.hitachi.co.jp Wed Sep 18 21:20:55 2002 From: sugita ＠ sdl.hitachi.co.jp (Yumiko Sugita) Date: Wed, 18 Sep 2002 21:20:55 +0900 Subject: [Lkst-develop] Release of LKST 1.3 Message-ID: <5.0.2.6.2.20020918210021.05244540@sdl99c> Dear all, I'd like to announce publication of Linux Kernel State Tracer (LKST) 1.3, 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, (1)It is possible to change dynamically which events are recorded. Users can obtain information about the events which they concern only interesting events. And it reduces the overhead of components which is not related with a fault. (2)It is possible to change each function invoked by each events. A default function invoked by events is just recording occuring of the events. But, if it is necessary, this function can be changed to another function. And LKST supports installing the function by using a kernel module LKST also supports a maskset, which controls what kind of events should be recorded, can be changed dynamically. For example, LKST usually traces a few events for good performance, and when the kernel be in a particular status, LKST can change a maskset to get more detail information. (3)It is possible to create new buffers and change to one of them. By changing to other buffer, Users can leave the information which they want. LKST binaries, source code and documents are available in the following site, https://sourceforge.net/projects/lkst/ http://sourceforge.jp/projects/lkst/ 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 lkst-users ＠ lists.sourceforge.jp To subscribe, please refer following URL, http://lists.sourceforge.net/lists/listinfo/lkst-users http://lists.sourceforge.jp/mailman/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 lkst-develop ＠ lists.sourceforge.jp With kindest regards, All of the LKST developers ---------------- Yumiko Sugita Hitachi,Ltd., Systems Development Laboratory From sugita ＠ sdl.hitachi.co.jp Wed Sep 18 21:16:52 2002 From: sugita ＠ sdl.hitachi.co.jp (Yumiko Sugita) Date: Wed, 18 Sep 2002 21:16:52 +0900 Subject: [Lkst-develop] Release of LKST 1.3 Message-ID: <5.0.2.6.2.20020918210556.0524e3d8@sdl99c> Dear all, I'd like to announce publication of Linux Kernel State Tracer (LKST) 1.3, 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, (1)It is possible to change dynamically which events are recorded. Users can obtain information about the events which they concern only interesting events. And it reduces the overhead of components which is not related with a fault. (2)It is possible to change each function invoked by each events. A default function invoked by events is just recording occuring of the events. But, if it is necessary, this function can be changed to another function. And LKST supports installing the function by using a kernel module LKST also supports a maskset, which controls what kind of events should be recorded, can be changed dynamically. For example, LKST usually traces a few events for good performance, and when the kernel be in a particular status, LKST can change a maskset to get more detail information. (3)It is possible to create new buffers and change to one of them. By changing to other buffer, Users can leave the information which they want. LKST binaries, source code and documents are available in the following site, https://sourceforge.net/projects/lkst/ http://sourceforge.jp/projects/lkst/ 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 lkst-users ＠ lists.sourceforge.jp To subscribe, please refer following URL, http://lists.sourceforge.net/lists/listinfo/lkst-users http://lists.sourceforge.jp/mailman/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 lkst-develop ＠ lists.sourceforge.jp With kindest regards, All of the LKST developers ---------------- Yumiko Sugita Hitachi,Ltd., Systems Development Laboratory From sugita ＠ sdl.hitachi.co.jp Wed Sep 18 21:22:55 2002 From: sugita ＠ sdl.hitachi.co.jp (Yumiko Sugita) Date: Wed, 18 Sep 2002 21:22:55 +0900 Subject: [Lkst-develop] LKST v1.3リリースのお知らせ Message-ID: <5.0.2.6.2.20020918211219.052c1f30@sdl99c> 各位 　Linux Kernel State Tracer (LKST) v1.3をリリースしましたのでお知らせ 致します。 　LKSTはデバッグおよび障害解析、性能解析を目的としたカーネル用イベント トレーサであり、下記の特徴を持っています。 （１）記録するイベントの動的な選択 ・その時点での目的にあった情報のみを採取することができ、障害に無関 　　係なイベント情報の採取によるオーバヘッドを削減できます。 （２）各イベントに対し、それを記録する関数の動的な変更 ・デフォルトでは多くのイベントに対し、イベント発生を記録する関数を割り 　　当てていますが、トレース中にこの関数を他の関数に変更できます。 　　・マスクセット(複数のイベントと各々に対する関数の定義)により一括して 　　切り替えることも可能です。これにより、平常時には最小限のトレースを 　　行ない、障害発生以降は関係するイベントの詳細情報の記録に切替える 　　などの運用が、容易に実現できます。 　　・これらの記録関数は、ユーザがカーネルの拡張モジュールとして組み 　　込むことも可能です。 （３）記録バッファの動的な作成・変更 　　・記録バッファを動的に作成し切替えることで、他のイベントの情報による 　　バッファの上書きを防ぎ、欲しい情報を残すことができます。 ――――――――――――――――――――― LKST のバイナリおよびソース、ドキュメントは下記の URL から入手できます。 https://sourceforge.net/projects/lkst/ http://sourceforge.jp/projects/lkst/ http://oss.hitachi.co.jp/sdl/english/lkst.html (現在更新中) 　なお、LKST v1.1がMiracle Linux v2.1に採用されています。Miracle Linux v2.1をお使いの方はパッチを当てることなくLKSTを使用できます。 ――――――――――――――――――――― LKST のアップデート等をお知らせするために、下記のML をご用意致して おります。 lkst-users ＠ lists.sourceforge.jp lkst-users ＠ lists.sourceforge.net 　本 ML のご購読には、下記 URL をご参照下さい。 http://lists.sourceforge.jp/mailman/listinfo/lkst-users http://lists.sourceforge.net/lists/listinfo/lkst-users 　コメント、バグレポートは、上記 ML か、開発者向けの下記ML までお願い 致します。 lkst-develop ＠ lists.sourceforge.jp lkst-develop ＠ lists.sourceforge.net LKST 開発チーム一同 *〜*〜*〜*〜*〜 Yumiko Sugita Hitachi, Ltd., Systems Development Laboratory Tel:+81-44-959-0258 Fax:+81-44-959-0855 　　　　　 〜*〜*〜*〜*〜* From sugita ＠ sdl.hitachi.co.jp Wed Sep 18 21:20:55 2002 From: sugita ＠ sdl.hitachi.co.jp (Yumiko Sugita) Date: Wed, 18 Sep 2002 21:20:55 +0900 Subject: [Lkst-develop] Release of LKST 1.3 Message-ID: <5.0.2.6.2.20020918210036.05287a40@sdl99c> Dear all, I'd like to announce publication of Linux Kernel State Tracer (LKST) 1.3, 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, (1)It is possible to change dynamically which events are recorded. Users can obtain information about the events which they concern only interesting events. And it reduces the overhead of components which is not related with a fault. (2)It is possible to change each function invoked by each events. A default function invoked by events is just recording occuring of the events. But, if it is necessary, this function can be changed to another function. And LKST supports installing the function by using a kernel module LKST also supports a maskset, which controls what kind of events should be recorded, can be changed dynamically. For example, LKST usually traces a few events for good performance, and when the kernel be in a particular status, LKST can change a maskset to get more detail information. (3)It is possible to create new buffers and change to one of them. By changing to other buffer, Users can leave the information which they want. LKST binaries, source code and documents are available in the following site, https://sourceforge.net/projects/lkst/ http://sourceforge.jp/projects/lkst/ 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 lkst-users ＠ lists.sourceforge.jp To subscribe, please refer following URL, http://lists.sourceforge.net/lists/listinfo/lkst-users http://lists.sourceforge.jp/mailman/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 lkst-develop ＠ lists.sourceforge.jp With kindest regards, All of the LKST developers ---------------- Yumiko Sugita Hitachi,Ltd., Systems Development Laboratory From sugita ＠ sdl.hitachi.co.jp Wed Sep 18 21:23:17 2002 From: sugita ＠ sdl.hitachi.co.jp (Yumiko Sugita) Date: Wed, 18 Sep 2002 21:23:17 +0900 Subject: [Lkst-develop] LKST v1.3リリースのお知らせ Message-ID: <5.0.2.6.2.20020918211201.052bc9b0@sdl99c> 各位 　Linux Kernel State Tracer (LKST) v1.3をリリースしましたのでお知らせ 致します。 　LKSTはデバッグおよび障害解析、性能解析を目的としたカーネル用イベント トレーサであり、下記の特徴を持っています。 （１）記録するイベントの動的な選択 ・その時点での目的にあった情報のみを採取することができ、障害に無関 　　係なイベント情報の採取によるオーバヘッドを削減できます。 （２）各イベントに対し、それを記録する関数の動的な変更 ・デフォルトでは多くのイベントに対し、イベント発生を記録する関数を割り 　　当てていますが、トレース中にこの関数を他の関数に変更できます。 　　・マスクセット(複数のイベントと各々に対する関数の定義)により一括して 　　切り替えることも可能です。これにより、平常時には最小限のトレースを 　　行ない、障害発生以降は関係するイベントの詳細情報の記録に切替える 　　などの運用が、容易に実現できます。 　　・これらの記録関数は、ユーザがカーネルの拡張モジュールとして組み 　　込むことも可能です。 （３）記録バッファの動的な作成・変更 　　・記録バッファを動的に作成し切替えることで、他のイベントの情報による 　　バッファの上書きを防ぎ、欲しい情報を残すことができます。 ――――――――――――――――――――― LKST のバイナリおよびソース、ドキュメントは下記の URL から入手できます。 https://sourceforge.net/projects/lkst/ http://sourceforge.jp/projects/lkst/ http://oss.hitachi.co.jp/sdl/english/lkst.html (現在更新中) 　なお、LKST v1.1がMiracle Linux v2.1に採用されています。Miracle Linux v2.1をお使いの方はパッチを当てることなくLKSTを使用できます。 ――――――――――――――――――――― LKST のアップデート等をお知らせするために、下記のML をご用意致して おります。 lkst-users ＠ lists.sourceforge.jp lkst-users ＠ lists.sourceforge.net 　本 ML のご購読には、下記 URL をご参照下さい。 http://lists.sourceforge.jp/mailman/listinfo/lkst-users http://lists.sourceforge.net/lists/listinfo/lkst-users 　コメント、バグレポートは、上記 ML か、開発者向けの下記ML までお願い 致します。 lkst-develop ＠ lists.sourceforge.jp lkst-develop ＠ lists.sourceforge.net LKST 開発チーム一同 *〜*〜*〜*〜*〜 Yumiko Sugita Hitachi, Ltd., Systems Development Laboratory Tel:+81-44-959-0258 Fax:+81-44-959-0855 　　　　　 〜*〜*〜*〜*〜* From sugita ＠ sdl.hitachi.co.jp Wed Sep 18 21:16:52 2002 From: sugita ＠ sdl.hitachi.co.jp (Yumiko Sugita) Date: Wed, 18 Sep 2002 21:16:52 +0900 Subject: [Lkst-develop] Release of LKST 1.3 Message-ID: <5.0.2.6.2.20020918210608.042e2238@sdl99c> Dear all, I'd like to announce publication of Linux Kernel State Tracer (LKST) 1.3, 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, (1)It is possible to change dynamically which events are recorded. Users can obtain information about the events which they concern only interesting events. And it reduces the overhead of components which is not related with a fault. (2)It is possible to change each function invoked by each events. A default function invoked by events is just recording occuring of the events. But, if it is necessary, this function can be changed to another function. And LKST supports installing the function by using a kernel module LKST also supports a maskset, which controls what kind of events should be recorded, can be changed dynamically. For example, LKST usually traces a few events for good performance, and when the kernel be in a particular status, LKST can change a maskset to get more detail information. (3)It is possible to create new buffers and change to one of them. By changing to other buffer, Users can leave the information which they want. LKST binaries, source code and documents are available in the following site, https://sourceforge.net/projects/lkst/ http://sourceforge.jp/projects/lkst/ 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 lkst-users ＠ lists.sourceforge.jp To subscribe, please refer following URL, http://lists.sourceforge.net/lists/listinfo/lkst-users http://lists.sourceforge.jp/mailman/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 lkst-develop ＠ lists.sourceforge.jp With kindest regards, All of the LKST developers ---------------- Yumiko Sugita Hitachi,Ltd., Systems Development Laboratory From sugita ＠ sdl.hitachi.co.jp Wed Sep 18 21:23:40 2002 From: sugita ＠ sdl.hitachi.co.jp (Yumiko Sugita) Date: Wed, 18 Sep 2002 21:23:40 +0900 Subject: [Lkst-develop] LKST v1.3リリースのお知らせ Message-ID: <5.0.2.6.2.20020918211210.052bc308@sdl99c> 各位 　Linux Kernel State Tracer (LKST) v1.3をリリースしましたのでお知らせ 致します。 　LKSTはデバッグおよび障害解析、性能解析を目的としたカーネル用イベント トレーサであり、下記の特徴を持っています。 （１）記録するイベントの動的な選択 ・その時点での目的にあった情報のみを採取することができ、障害に無関 　　係なイベント情報の採取によるオーバヘッドを削減できます。 （２）各イベントに対し、それを記録する関数の動的な変更 ・デフォルトでは多くのイベントに対し、イベント発生を記録する関数を割り 　　当てていますが、トレース中にこの関数を他の関数に変更できます。 　　・マスクセット(複数のイベントと各々に対する関数の定義)により一括して 　　切り替えることも可能です。これにより、平常時には最小限のトレースを 　　行ない、障害発生以降は関係するイベントの詳細情報の記録に切替える 　　などの運用が、容易に実現できます。 　　・これらの記録関数は、ユーザがカーネルの拡張モジュールとして組み 　　込むことも可能です。 （３）記録バッファの動的な作成・変更 　　・記録バッファを動的に作成し切替えることで、他のイベントの情報による 　　バッファの上書きを防ぎ、欲しい情報を残すことができます。 ――――――――――――――――――――― LKST のバイナリおよびソース、ドキュメントは下記の URL から入手できます。 https://sourceforge.net/projects/lkst/ http://sourceforge.jp/projects/lkst/ http://oss.hitachi.co.jp/sdl/english/lkst.html (現在更新中) 　なお、LKST v1.1がMiracle Linux v2.1に採用されています。Miracle Linux v2.1をお使いの方はパッチを当てることなくLKSTを使用できます。 ――――――――――――――――――――― LKST のアップデート等をお知らせするために、下記のML をご用意致して おります。 lkst-users ＠ lists.sourceforge.jp lkst-users ＠ lists.sourceforge.net 　本 ML のご購読には、下記 URL をご参照下さい。 http://lists.sourceforge.jp/mailman/listinfo/lkst-users http://lists.sourceforge.net/lists/listinfo/lkst-users 　コメント、バグレポートは、上記 ML か、開発者向けの下記ML までお願い 致します。 lkst-develop ＠ lists.sourceforge.jp lkst-develop ＠ lists.sourceforge.net LKST 開発チーム一同 *〜*〜*〜*〜*〜 Yumiko Sugita Hitachi, Ltd., Systems Development Laboratory Tel:+81-44-959-0258 Fax:+81-44-959-0855 　　　　　 〜*〜*〜*〜*〜* From sugita ＠ sdl.hitachi.co.jp Wed Sep 18 21:16:52 2002 From: sugita ＠ sdl.hitachi.co.jp (Yumiko Sugita) Date: Wed, 18 Sep 2002 21:16:52 +0900 Subject: [Lkst-develop] Release of LKST 1.3 Message-ID: <5.0.2.6.2.20020918210648.052958b8@sdl99c> Dear all, I'd like to announce publication of Linux Kernel State Tracer (LKST) 1.3, 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, (1)It is possible to change dynamically which events are recorded. Users can obtain information about the events which they concern only interesting events. And it reduces the overhead of components which is not related with a fault. (2)It is possible to change each function invoked by each events. A default function invoked by events is just recording occuring of the events. But, if it is necessary, this function can be changed to another function. And LKST supports installing the function by using a kernel module LKST also supports a maskset, which controls what kind of events should be recorded, can be changed dynamically. For example, LKST usually traces a few events for good performance, and when the kernel be in a particular status, LKST can change a maskset to get more detail information. (3)It is possible to create new buffers and change to one of them. By changing to other buffer, Users can leave the information which they want. LKST binaries, source code and documents are available in the following site, https://sourceforge.net/projects/lkst/ http://sourceforge.jp/projects/lkst/ 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 lkst-users ＠ lists.sourceforge.jp To subscribe, please refer following URL, http://lists.sourceforge.net/lists/listinfo/lkst-users http://lists.sourceforge.jp/mailman/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 lkst-develop ＠ lists.sourceforge.jp With kindest regards, All of the LKST developers ---------------- Yumiko Sugita Hitachi,Ltd., Systems Development Laboratory From sugita ＠ sdl.hitachi.co.jp Wed Sep 18 21:17:55 2002 From: sugita ＠ sdl.hitachi.co.jp (Yumiko Sugita) Date: Wed, 18 Sep 2002 21:17:55 +0900 Subject: [Lkst-develop] Release of LKST 1.3 Message-ID: <5.0.2.6.2.20020918210701.052a6760@sdl99c> Dear all, I'd like to announce publication of Linux Kernel State Tracer (LKST) 1.3, 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, (1)It is possible to change dynamically which events are recorded. Users can obtain information about the events which they concern only interesting events. And it reduces the overhead of components which is not related with a fault. (2)It is possible to change each function invoked by each events. A default function invoked by events is just recording occuring of the events. But, if it is necessary, this function can be changed to another function. And LKST supports installing the function by using a kernel module LKST also supports a maskset, which controls what kind of events should be recorded, can be changed dynamically. For example, LKST usually traces a few events for good performance, and when the kernel be in a particular status, LKST can change a maskset to get more detail information. (3)It is possible to create new buffers and change to one of them. By changing to other buffer, Users can leave the information which they want. LKST binaries, source code and documents are available in the following site, https://sourceforge.net/projects/lkst/ http://sourceforge.jp/projects/lkst/ 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 lkst-users ＠ lists.sourceforge.jp To subscribe, please refer following URL, http://lists.sourceforge.net/lists/listinfo/lkst-users http://lists.sourceforge.jp/mailman/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 lkst-develop ＠ lists.sourceforge.jp With kindest regards, All of the LKST developers ---------------- Yumiko Sugita Hitachi,Ltd., Systems Development Laboratory From robert ＠ schwebel.de Thu Sep 19 14:58:44 2002 From: robert ＠ schwebel.de (Robert Schwebel) Date: Thu, 19 Sep 2002 07:58:44 +0200 Subject: [Lkst-develop] Re: Release of LKST 1.3 In-Reply-To: <5.0.2.6.2.20020918210036.05287a40@sdl99c> References: <5.0.2.6.2.20020918210036.05287a40@sdl99c> Message-ID: <20020919055843.GC10773@pengutronix.de> On Wed, Sep 18, 2002 at 09:20:55PM +0900, Yumiko Sugita wrote: > I'd like to announce publication of Linux Kernel State Tracer (LKST) > 1.3, which is a tracer for Linux kernel. Can you tell us what's the difference between this and the Linux Trace Toolkit (LTT)? Robert -- Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de Pengutronix - Linux Solutions for Science and Industry Braunschweiger Str. 79, 31134 Hildesheim, Germany Handelsregister: Amtsgericht Hildesheim, HRA 2686 Phone: +49-5121-28619-0 | Fax: +49-5121-28619-4 From sugita ＠ sdl.hitachi.co.jp Thu Sep 26 21:36:52 2002 From: sugita ＠ sdl.hitachi.co.jp (Yumiko Sugita) Date: Thu, 26 Sep 2002 21:36:52 +0900 Subject: [Lkst-develop] Re: Release of LKST 1.3 In-Reply-To: <20020919055843.GC10773@pengutronix.de> References: <5.0.2.6.2.20020918210036.05287a40@sdl99c> <5.0.2.6.2.20020918210036.05287a40@sdl99c> Message-ID: <5.0.2.6.2.20020926182552.0506a898@sdl99c> Hello, Robert Thank you for your inquiry. I apologize for the delay in replying. Let me first explain the background of our development work. We began development of the Linux Kernel State Tracer (LKST) in response to a domestic need to improve Reliability, Availability, and Serviceability (RAS) with respect to enterprise systems. The following requirements were applied to LKST: * Capable of handling a variety of information about system errors. * Little trace overhead (or To control trace overhead) * Short development time As we had to achieve a short development time, we elected to develop LKST using our own methodology (based on know-how of tracer development that we carried out for other OS's) different from other known tools such as LTT. # This is not to say that we developed all functions on our own. #LKST at present connects with Kernel Hooks (GKHI) and LKCD. Consequently, LKST, which is oriented to enterprise systems, has the following features different from those of LTT. # These LKST features are also being enhanced at this time. (1) Little overhead and good scalability when tracing on a large-scale SMP system * To make lock mechanism overhead as little as possible, we designed that the buffers are not shared among CPUs. (2) Easy to extend/expand the function (User-based extendibility) * Without recompiling kernel, user can change/add/modify the kind of events and information to be recorded at anytime. For example, LKST usually traces very few events for the purpose of good performance. Once the kernel get into the particular status that user specified, LKST will trace and record more detail information. (3) Preservation of trace information * Recovery of trace information collected at the time of a system crash in connection with LKCD. * Saving of specific event information during tracing. For example, switching to another buffer after the occurrence of a specific event enables the information on that event to be left in the previous buffer. (4) Collection of even more kernel event information * Information on more than 50 kernel events can be collected for kernel debugging. The demand for RAS functions in Linux should grow in the years to come. It is our hope that LKST becomes one means of implementing such functions. Best regards, ---------------- Yumiko Sugita Hitachi,Ltd., Systems Development Laboratory At 07:58 02/09/19 +0200, Robert Schwebel wrote: >On Wed, Sep 18, 2002 at 09:20:55PM +0900, Yumiko Sugita wrote: > > I'd like to announce publication of Linux Kernel State Tracer (LKST) > > 1.3, which is a tracer for Linux kernel. > >Can you tell us what's the difference between this and the Linux Trace >Toolkit (LTT)? > >Robert >-- > Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de > Pengutronix - Linux Solutions for Science and Industry > Braunschweiger Str. 79, 31134 Hildesheim, Germany > Handelsregister: Amtsgericht Hildesheim, HRA 2686 > Phone: +49-5121-28619-0 | Fax: +49-5121-28619-4 >_______________________________________________ >Lkst-develop mailing list >Lkst-develop ＠ lists.sourceforge.jp >http://lists.sourceforge.jp/cgi-bin/mailman/listinfo/lkst-develop From karim ＠ opersys.com Sat Sep 28 00:48:19 2002 From: karim ＠ opersys.com (Karim Yaghmour) Date: Fri, 27 Sep 2002 11:48:19 -0400 Subject: [Lkst-develop] Re: Release of LKST 1.3 References: <5.0.2.6.2.20020918210036.05287a40@sdl99c> <5.0.2.6.2.20020918210036.05287a40@sdl99c> <5.0.2.6.2.20020926182552.0506a898@sdl99c> Message-ID: <3D947DC3.EEC6C0A6@opersys.com> Just a couple of general observations here. Yumiko Sugita wrote: > Consequently, LKST, which is oriented to enterprise systems, > has the following features different from those of LTT. > # These LKST features are also being enhanced at this time. > > (1) Little overhead and good scalability when tracing on a large-scale > SMP system > * To make lock mechanism overhead as little as possible, we > designed that the buffers are not shared among CPUs. I was wondering whether you followed the recent discussion about LTT on the LKML? Clearly this is not a problem for LTT since we don't use any form of locking whatsoever anymore. IBM's work on the lockless scheme has solved this problem and their current work on the per-CPU buffering solves the rest of the issue. > (2) Easy to extend/expand the function (User-based extendibility) > * Without recompiling kernel, user can change/add/modify the kind > of events and information to be recorded at anytime. Ditto with LTT. > For example, LKST usually traces very few events for the purpose > of good performance. Once the kernel get into the particular status > that user specified, LKST will trace and record more detail information. This implies callbacks, which do exist in LTT and which Ingo Molnar explicitly asked us to remove. > (3) Preservation of trace information > * Recovery of trace information collected at the time of a system crash > in connection with LKCD. Connection with LKCD is really not a problem, but this points to the main purpose of the tool, which in the case of LKCD is kernel debugging. LTT isn't aimed as a kernel debugger, so although LKCD is on our to-do list, it's certainly not our priority. As for handling multiple output streams (which LKCD can be one of them), we already have very detailed plans on how LTT is going to integrate this (as I've mentioned a number of times before on this list). However, before we go down this road we need to make sure that the core tracing functionality is lightweight and fits the general requirements set for kernel code. Once this core lighweight functionality is there, we can build a rich and solid feature set around it. > * Saving of specific event information during tracing. > For example, switching to another buffer after the occurrence of > a specific event enables the information on that event to be left > in the previous buffer. Again, callbacks and triggers. A while back, I had written a state machine engine for LTT. Basically, you could provide it with an event-driven state machine and it would callback your functions depending on the sequence of events. All of this obviously implies callbacks, which, as I said earlier, we've been explicitly asked to remove. > (4) Collection of even more kernel event information > * Information on more than 50 kernel events can be collected for > kernel debugging. Well, I think this is where LTT and LKST cannot be compared. If LKST is a kernel debugging tool, as it has always been advertised, then any comparison of LKST should be made with the other tracing tools which are used for kernel debugging, such as the ones mentioned by Ingo and Andi earlier on this list. LTT was built from the ground up to help users understand the dynamic behavior of the system. As such, it cannot be compared to any kernel debugging tool since it isn't one. > The demand for RAS functions in Linux should grow in the years to come. > It is our hope that LKST becomes one means of implementing such functions. There was a RAS BoF at the OLS this year where tracing was intensively discussed. All the attendees agreed to unify their efforts around LTT. At this meeting, Richard Moore of IBM presented a tracing to-do list (http://opersys.com/LTT/ltt-to-do-list.txt) which we are using a basic check list for our ongoing work. Instead of implementing yet another tracing system, I think that the LKST team would benefit much from contributing to LTT, which has already a proven track record and has been adopted by the community as much as the industry. Karim =================================================== Karim Yaghmour karim ＠ opersys.com Embedded and Real-Time Linux Expert ===================================================