diff options
Diffstat (limited to 'lket.5.in')
| -rw-r--r-- | lket.5.in | 36 |
1 files changed, 18 insertions, 18 deletions
@@ -204,10 +204,10 @@ Where is the combination of: .SAMPLE -((cmd->device->host->host_no & 0xFF) << 24) | -((cmd->device->channel & 0xFF) << 16) | -((cmd->device->lun & 0xFF) << 8) | -(cmd->device->id & 0xFF) +((cmd\->device\->host\->host_no & 0xFF) << 24) | +((cmd\->device\->channel & 0xFF) << 16) | +((cmd\->device\->lun & 0xFF) << 8) | +(cmd\->device\->id & 0xFF) .ESAMPLE .TP @@ -483,25 +483,25 @@ Data format is: By default, LKET will log the trace data in binary format. -To get a better performance for binary tracing, the "-b" option should -be turned on for stap and thus -M option has to be added to stop stpd +To get a better performance for binary tracing, the "\-b" option should +be turned on for stap and thus \-M option has to be added to stop stpd merging per-cpu files. You could use the command -.I lket-b2a +.I lket\-b2a to convert the binary trace data generated by LKET into readable data in ascii format. -.I lket-b2a +.I lket\-b2a uses the pre-cpu binary trace data files as inputs, and generates an output file named .I lket.out -You should use "stap -b -M" with LKET to get those pre-cpu files +You should use "stap \-b \-M" with LKET to get those pre-cpu files (stpd_cpu*) before using it. If you want LKET to log trace data in ASCII format directly, you should: .SAMPLE -stap -D ASCII_TRACE ... +stap \-D ASCII_TRACE ... .ESAMPLE .SH EVENT REGISTER @@ -572,9 +572,9 @@ data for that event? LKET provides a way to do this without modifying the codes in the tapset of that event hook. You can simply use printf to trace -extra data. For example, supposing you want to trace sk_buff->mac_len -and sk_buff->priority besides the sk_buff->len, sk_buff->protocol and -sk_buff->truesize for the +extra data. For example, supposing you want to trace sk_buff\->mac_len +and sk_buff\->priority besides the sk_buff\->len, sk_buff\->protocol and +sk_buff\->truesize for the .B netdev event hooks: @@ -586,7 +586,7 @@ probe register_event } probe addevent.netdev.transmit { - printf("%4b%4b", $skb->mac_len, $skb->priority) + printf("%4b%4b", $skb\->mac_len, $skb\->priority) } .ESAMPLE @@ -596,16 +596,16 @@ Here are some examples of using LKET: .TP To turn on all event hooks: -stap -e "probe addevent.* {}" -bM +stap \-e "probe addevent.* {}" \-bM .TP To probe syscall: -stap -e "probe addevent.syscall {}" -bM +stap \-e "probe addevent.syscall {}" \-bM .TP To only probe syscall.entry: -stap -e "probe addevent.syscall.entry {}" -bM +stap \-e "probe addevent.syscall.entry {}" \-bM .TP To probe netdev transmition and log extra data of mac_len and priority: -stap -e "probe addevent.netdev.transmit { printf(\\"%4b%4b\\", $skb->mac_len, $skb->priority) }" -bM +stap \-e "probe addevent.netdev.transmit { printf(\\"%4b%4b\\", $skb\->mac_len, $skb\->priority) }" \-bM .SH SEE ALSO .IR stap (1) |