Features/Tracing: Difference between revisions
| Line 9: | Line 9: | ||
== Description == | == Description == | ||
Light-weight logging at points of interest inside QEMU can improve common debugging and performance analysis tasks. Currently the QEMU community has to rely on debuggers, which may be invasive and slow, or printfs, which are not suited for high-frequency logging. | |||
Tracing addresses these observability shortcomings with an easily extended set of trace events in QEMU that can be enabled/disable at runtime. | |||
== Status == | == Status == | ||
Revision as of 13:22, 6 July 2010
Summary
Tracing aids debugging and performance analysis with a set of light-weight events throughout QEMU that are logged when hit.
Owner
- Name: Stefan Hajnoczi
- Email: stefanha@linux.vnet.ibm.com
Description
Light-weight logging at points of interest inside QEMU can improve common debugging and performance analysis tasks. Currently the QEMU community has to rely on debuggers, which may be invasive and slow, or printfs, which are not suited for high-frequency logging.
Tracing addresses these observability shortcomings with an easily extended set of trace events in QEMU that can be enabled/disable at runtime.