aboutsummaryrefslogtreecommitdiff
path: root/docs/tracing.txt
diff options
context:
space:
mode:
authorEiichi Tsukata <eiichi.tsukata.xh@hitachi.com>2013-04-11 20:25:15 +0900
committerStefan Hajnoczi <stefanha@redhat.com>2013-05-03 13:58:09 +0200
commit781e9545dbe54d2f0a530edbf48fd0ac1e77244c (patch)
tree9f89f26c7f52ff8cfca0997e8d7849dd242dc79b /docs/tracing.txt
parentb76ac80a5ca9f2e19405419172c0dcaf0370d4f5 (diff)
downloadqemu-781e9545dbe54d2f0a530edbf48fd0ac1e77244c.zip
qemu-781e9545dbe54d2f0a530edbf48fd0ac1e77244c.tar.gz
qemu-781e9545dbe54d2f0a530edbf48fd0ac1e77244c.tar.bz2
trace: Add ftrace tracing backend
This patch adds a ftrace tracing backend which sends trace event to ftrace marker file. You can effectively compare qemu trace data and kernel(especially, kvm.ko when using KVM) trace data. The ftrace backend is restricted to Linux only. To try out the ftrace backend: $ ./configure --trace-backend=ftrace $ make if you use KVM, enable kvm events in ftrace: # sudo echo 1 > /sys/kernel/debug/tracing/events/kvm/enable After running qemu by root user, you can get the trace: # cat /sys/kernel/debug/tracing/trace Signed-off-by: Eiichi Tsukata <eiichi.tsukata.xh@hitachi.com> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'docs/tracing.txt')
0 files changed, 0 insertions, 0 deletions