diff options
| -rw-r--r-- | lket.5.in | 12 |
1 files changed, 6 insertions, 6 deletions
@@ -22,7 +22,7 @@ library available on SystemTap. Its goal is to utilize the dynamic probing capabilities provided through SystemTap to create a set of standard hooks that probe pre-defined places in the kernel. It can be used to collect important information that can be used as a starting point to analyze -a performance problem in their system. +a performance problem in the system. The LKET tapsets are designed to only trace the events selected by the user. Once the data has been collected, it is then post-processed @@ -32,8 +32,9 @@ various different ways to generate simple to complex reports. .SH EVENT HOOKS The following sections enumerate the variety of event hooks implemented -in LKET and their trace data format. Each event hook contains common data -as well as some data that is specific to that event hook. +in LKET and their trace data format. The trace data generated by different +event hooks contains common data +as well as some data specific to that event hook. the INT8, INT16, INT32, INT64 and STRING appeared in trace data format represents 8-bit, 16-bit, 32-bit, 64-bit binary data and NULL-terminated @@ -44,12 +45,11 @@ The data common(i.e. in the following subsecions) to all event hooks is: .RS -.I GroupID(INT8), hookID(INT8), second(INT32), usec(INT32), tgid(INT32), -.I ppid(INT32), pid(INT32), cpu_id(INT8) +usec(INT64),(pid<<32 | groupID<<24 | hookID<<16 | cpu_id<<8)(INT64) .RE Each event hook group is a collection of those hooks that have -similarities of what they could trace. And the ID of each event hook +similarities of what they could trace. And the ID of each event hook (HookID) is defined in the context of its corresponding group. .SS SYSTEM CALLS (GROUPID=2) |