diff options
| author | Lluís <xscript@gmx.net> | 2011-08-31 20:31:31 +0200 |
|---|---|---|
| committer | Stefan Hajnoczi <stefanha@linux.vnet.ibm.com> | 2011-09-01 10:34:54 +0100 |
| commit | 23d15e860b33819ad76092fbb32577542fe0c44d (patch) | |
| tree | 20c99fb621ab3c063c60029e69c8df744c6be0eb /docs/tracing.txt | |
| parent | 31965ae27bc11e90674be12584bb201b83df5aef (diff) | |
trace: add "-trace events" argument to control initial state
The "-trace events" argument can be used to provide a file with a list of trace
event names that will be enabled prior to starting execution, thus providing
early tracing.
This saves the user from manually toggling event states through the monitor
interface or whichever backend-specific interface.
Signed-off-by: Lluís Vilanova <vilanova@ac.upc.edu>
Diffstat (limited to 'docs/tracing.txt')
| -rw-r--r-- | docs/tracing.txt | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/docs/tracing.txt b/docs/tracing.txt index 41eb8e6fe..455da3796 100644 --- a/docs/tracing.txt +++ b/docs/tracing.txt @@ -138,6 +138,10 @@ This functionality is also provided through monitor commands: * trace-event NAME on|off Enable/disable a given trace event. +The "-trace events=<file>" command line argument can be used to enable the +events listed in <file> from the very beginning of the program. This file must +contain one event name per line. + == Trace backends == The "tracetool" script automates tedious trace event code generation and also |