From e64dd5efb2c6d522a3bc9d096cd49a4e53f0ae10 Mon Sep 17 00:00:00 2001 From: Eiichi Tsukata Date: Thu, 11 Apr 2013 20:25:16 +0900 Subject: trace: document ftrace backend Add documentation of ftrace backend. Signed-off-by: Eiichi Tsukata Signed-off-by: Stefan Hajnoczi --- docs/tracing.txt | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) (limited to 'docs') diff --git a/docs/tracing.txt b/docs/tracing.txt index cf53c173ec..60ff9c5e6e 100644 --- a/docs/tracing.txt +++ b/docs/tracing.txt @@ -175,6 +175,22 @@ unless you have specific needs for more advanced backends. The "simple" backend currently does not capture string arguments, it simply records the char* pointer value instead of the string that is pointed to. +=== Ftrace === + +The "ftrace" backend writes trace data to ftrace marker. This effectively +sends trace events to ftrace ring buffer, and you can compare qemu trace +data and kernel(especially kvm.ko when using KVM) trace data. + +if you use KVM, enable kvm events in ftrace: + + # 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 + +Restriction: "ftrace" backend is restricted to Linux only. + ==== Monitor commands ==== * trace-file on|off|flush|set -- cgit v1.2.1