Commit 670a6aa8 authored by Brendan Gregg's avatar Brendan Gregg

docs for offcputime -u

parent d364d044
......@@ -2,7 +2,7 @@
.SH NAME
offcputime \- Summarize off-CPU time by kernel stack trace. Uses Linux eBPF/bcc.
.SH SYNOPSIS
.B offcputime [\-h] [\-p PID] [\-i INTERVAL] [\-T] [duration]
.B offcputime [\-h] [\-u] [\-p PID] [\-i INTERVAL] [\-T] [duration]
.SH DESCRIPTION
This program shows kernel stack traces and task names that were blocked and
"off-CPU", and the total duration they were blocked: their "off-CPU time".
......@@ -33,6 +33,9 @@ CONFIG_BPF and bcc.
\-h
Print usage message.
.TP
\-u
Only trace user threads (not kernel threads).
.TP
\-v
Show raw addresses.
.TP
......
......@@ -3,7 +3,7 @@
# offcputime Summarize off-CPU time by kernel stack trace
# For Linux, uses BCC, eBPF.
#
# USAGE: offcputime [-h] [-p PID] [-i INTERVAL] [-T] [duration]
# USAGE: offcputime [-h] [-u] [-p PID] [-i INTERVAL] [-T] [duration]
#
# The current implementation uses an unrolled loop for x86_64, and was written
# as a proof of concept. This implementation should be replaced in the future
......
......@@ -723,8 +723,8 @@ creating your "off-CPU time flame graphs".
USAGE message:
./offcputime --help
usage: offcputime [-h] [-p PID] [-v] [-f] [duration]
# ./offcputime -h
usage: offcputime [-h] [-u] [-p PID] [-v] [-f] [duration]
Summarize off-CPU time by kernel stack trace
......@@ -733,6 +733,7 @@ positional arguments:
optional arguments:
-h, --help show this help message and exit
-u, --useronly user threads only (no kernel threads)
-p PID, --pid PID trace this PID only
-v, --verbose show raw addresses
-f, --folded output folded format
......@@ -741,4 +742,5 @@ examples:
./offcputime # trace off-CPU stack time until Ctrl-C
./offcputime 5 # trace for 5 seconds only
./offcputime -f 5 # 5 seconds, and output in folded format
./offcputime -u # don't include kernel threads (user only)
./offcputime -p 185 # trace fo PID 185 only
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment