提交 03727e6a 编写于 作者: L Lluís 提交者: Stefan Hajnoczi

trace: [simple] disable all trace points by default

Note that this refers to the backend-specific state (whether the output must be
generated), not the event "disabled" property (which always uses the "nop"
backend).
Signed-off-by: NLluís Vilanova <vilanova@ac.upc.edu>
上级 dd215f64
......@@ -12,11 +12,16 @@ for debugging, profiling, and observing execution.
./configure --trace-backend=simple
make
2. Run the virtual machine to produce a trace file:
2. Create a file with the events you want to trace:
qemu ... # your normal QEMU invocation
echo bdrv_aio_readv > /tmp/events
echo bdrv_aio_writev >> /tmp/events
3. Pretty-print the binary trace file:
3. Run the virtual machine to produce a trace file:
qemu -trace events=/tmp/events ... # your normal QEMU invocation
4. Pretty-print the binary trace file:
./simpletrace.py trace-events trace-*
......
......@@ -221,15 +221,10 @@ EOF
linetoc_simple()
{
local name state
local name
name=$(get_name "$1")
if has_property "$1" "disable"; then
state="0"
else
state="1"
fi
cat <<EOF
{.tp_name = "$name", .state=$state},
{.tp_name = "$name", .state=0},
EOF
simple_event_num=$((simple_event_num + 1))
}
......
......@@ -17,9 +17,6 @@
# Example: qemu_malloc(size_t size) "size %zu"
#
# The "disable" keyword will build without the trace event.
# In case of 'simple' trace backend, it will allow the trace event to be
# compiled, but this would be turned off by default. It can be toggled on via
# the monitor.
#
# The <name> must be a valid as a C function name.
#
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册