summaryrefslogtreecommitdiff
path: root/tools/kvm/kvm_stat/kvm_stat.txt
diff options
context:
space:
mode:
authorJanosch Frank <frankja@linux.vnet.ibm.com>2016-05-18 13:26:24 +0200
committerPaolo Bonzini <pbonzini@redhat.com>2016-05-25 16:12:06 +0200
commitf0cf040f842242d55744c2606e8b7177507fbbb0 (patch)
treef277b06f090e47953d50e88db8ec1d13d1a585bf /tools/kvm/kvm_stat/kvm_stat.txt
parent536a6f88c49dd739961ffd53774775afed852c83 (diff)
tools: kvm_stat: Introduce pid monitoring
Having stats for single VMs can help to determine the problem of a VM without the need of running other tools like perf. The tracepoints already allowed pid level monitoring, but kvm_stat didn't have support for it till now. Support for the newly implemented debugfs vm monitoring was also implemented. Signed-off-by: Janosch Frank <frankja@linux.vnet.ibm.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'tools/kvm/kvm_stat/kvm_stat.txt')
-rw-r--r--tools/kvm/kvm_stat/kvm_stat.txt6
1 files changed, 4 insertions, 2 deletions
diff --git a/tools/kvm/kvm_stat/kvm_stat.txt b/tools/kvm/kvm_stat/kvm_stat.txt
index 8dcb48aaca50..b92a153d7115 100644
--- a/tools/kvm/kvm_stat/kvm_stat.txt
+++ b/tools/kvm/kvm_stat/kvm_stat.txt
@@ -23,8 +23,6 @@ The set of KVM kernel module trace events may be specific to the kernel version
or architecture. It is best to check the KVM kernel module source code for the
meaning of events.
-Note that trace events are counted globally across all running guests.
-
OPTIONS
-------
-1::
@@ -44,6 +42,10 @@ OPTIONS
--debugfs::
retrieve statistics from debugfs
+-p<pid>::
+--pid=<pid>::
+ limit statistics to one virtual machine (pid)
+
-f<fields>::
--fields=<fields>::
fields to display (regex)