aboutsummaryrefslogtreecommitdiff
path: root/qemu-barrier.h
diff options
context:
space:
mode:
authorStefan Hajnoczi <stefanha@linux.vnet.ibm.com>2012-03-09 14:13:40 +0000
committerMarcelo Tosatti <mtosatti@redhat.com>2012-04-12 19:01:41 -0300
commitb3c09bde4842f1b157bc4431135aad4f2031e312 (patch)
tree3a7033ec3616726d6b01f34a4cdc17c15aa091fe /qemu-barrier.h
parentdadc1064c348545695b8a14d9dc72ccaa2983be7 (diff)
downloadqemu-b3c09bde4842f1b157bc4431135aad4f2031e312.zip
qemu-b3c09bde4842f1b157bc4431135aad4f2031e312.tar.gz
qemu-b3c09bde4842f1b157bc4431135aad4f2031e312.tar.bz2
kvm: add flightrecorder script
The kvm kernel module includes a number of trace events which can be useful when debugging system behavior. Even on production systems these trace events can be used to observe guest behavior and identify the source of problems. The kvm_flightrecorder script is a command-line wrapper for the /sys/kernel/debug/tracing interface. Kernel symbols do not need to be installed. This script captures a fixed-size buffer of KVM trace events. Recent events overwrite the oldest events when the buffer size is exceeded and it is possible to leave KVM tracing enabled for any period of time with just a fixed-size buffer. If the buffer is large enough this script is a useful tool for collecting detailed information after an issue occurs with a guest. Hence the name "flight recorder". The script can also be used in 'tail' mode to simply view KVM trace events as they occur. This is handy for development and to ensure that the guest is indeed running. Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com> Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
Diffstat (limited to 'qemu-barrier.h')
0 files changed, 0 insertions, 0 deletions