From: eLinux.org

Linux Kernel State Tracer

Table Of Contents:

Contents

• 1 Description
  • 1.1 Rationale
• 2 Resources
  • 2.1 Projects
  • 2.2 Documents and presentations
  • 2.3 Specifications
• 3 Downloads
  • 3.1 Patch
  • 3.2 Utility programs
• 4 How To Use
• 5 How to validate
• 6 Sample Results
  • 6.1 Case Study 1
  • 6.2 Case Study 2
• 7 Status
• 8 Future Work/Action Items

Description

[This section describes the technology ….]

LKST is Kernel State Tracer for Linux in order to keep track of Kernel
Event such as:

 - Process Management
 - Interrupt
 - Exceptions
 - System Calls
 - Memory Managements
 - Networking: sending packets, receiving packets
 - Sys V IPC
 - Locks
 - Timer
 - Oops

Originally LKST is developed for Linux Enterprise Systems and now we
have port it to Reference Boards for Embedded Systems and currently SH4
port(RTS7751R2D), MIPS/TX49 port (RBHMA4400CE) and ARM/OMAP port (TI
OMAP INNOVATOR/OSK) are available.

Rationale

LKST is one of a number of tracing systems available for the Linux
kernel. Such event tracing systems are very useful for analyzing kernel
behaviour, and learning how interrupts, kernel threads and user-space
applications interact on the system.

Resources

Projects

Here is some information about LKST:

• project home page:
  http://lkst.sourceforge.net/

Documents and presentations

• Media:CELF_LKST_SH_Presen-2005-1.pdf
  • presentation given by Hitachi at CELF Jan 2005 technical
    conference.
• Media:CELF_LKST_SH_Lineo-2005-2.pdf
  • presentation given by Lineo at CELF Jan 2005 technical conference.
• Media:HITACHI-LKST-CELF-200601.pdf
  • presentation given at International Technical Conference, June
    2006
• Media:CELFTokyoJam6_LkstUpdate_Lineo.pdf
  • presentation ‘Features of lkslogtools’ given at CELF Jan 2006
    technical jamboree (6)

Specifications

Downloads

Patch

• You can acquire patches at:
  http://sourceforge.net/projects/lkst/
• and click the link of |Patches|:
  http://sourceforge.net/tracker/?group_id=41854&atid=431465

Utility programs

[other programs, user-space, test, etc. related to this technology]

How To Use

How to validate

[put references to test plans, scripts, methods, etc. here]

Sample Results

[Examples of use with measurement of the effects.]

Case Study 1

Case Study 2

Status

• Status: [implemented]

 (one of: not started, researched, implemented, measured, documented, accepted)

• Architecture Support:

  (for each arch, one of: unknown, patches apply, compiles, runs, works, accepted)

• • i386: works
  • x86_64: works
  • ia64: works
  • ARM: runs
  • PPC: unknown
  • MIPS: runs
  • SH: runs

Future Work/Action Items

Here is a list of things that could be worked on for this feature:

Category:

• Development
  Tools