| commit | bcec43324d02d586a8bc0c9093623636e870ad19 | |
| author | Stefan Hajnoczi <stefanha@linux.vnet.ibm.com> | |
| Tue, 27 Sep 2011 08:00:22 +0000 (27 09:00 +0100) | ||
| committer | Stefan Hajnoczi <stefanha@linux.vnet.ibm.com> | |
| Mon, 12 Mar 2012 10:12:34 +0000 (12 10:12 +0000) | ||
| tree | 000a968dc4e7fd5fab3d7766b48dec5e3dd03886 | treesnapshot (tar.gz zip) |
| parent | b7d66a761f44a725352e19b64c587924647e6f83 | commitdiff |
tracetool: Omit useless QEMU_*_ENABLED() check
SystemTap provides a "semaphore" that can optionally be tested before
executing a trace event. The purpose of this mechanism is to skip
expensive tracing code when the trace event is disabled.
For example, some applications may have trace events that format or
convert strings for trace events. This expensive processing should only
be done in the case where the trace event is enabled.
Since QEMU's generated trace events never have such special-purpose
code, there is no reason to add the semaphore check.
Reviewed-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
SystemTap provides a "semaphore" that can optionally be tested before
executing a trace event. The purpose of this mechanism is to skip
expensive tracing code when the trace event is disabled.
For example, some applications may have trace events that format or
convert strings for trace events. This expensive processing should only
be done in the case where the trace event is enabled.
Since QEMU's generated trace events never have such special-purpose
code, there is no reason to add the semaphore check.
Reviewed-by: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
| scripts/tracetool | diffblobblamehistory |