Commit b73e8bd4 authored by Dr. David Alan Gilbert's avatar Dr. David Alan Gilbert Committed by Stefan Hajnoczi

Tracing docs fix configure option and description

Fix the example trace configure option.
Update the text to say that multiple backends are allowed and what
happens when multiple backends are enabled.
Signed-off-by: default avatarDr. David Alan Gilbert <dgilbert@redhat.com>
Message-id: 1412691161-31785-1-git-send-email-dgilbert@redhat.com
Signed-off-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
parent 1aba4be9
...@@ -139,12 +139,12 @@ events are not tightly coupled to a specific trace backend, such as LTTng or ...@@ -139,12 +139,12 @@ events are not tightly coupled to a specific trace backend, such as LTTng or
SystemTap. Support for trace backends can be added by extending the "tracetool" SystemTap. Support for trace backends can be added by extending the "tracetool"
script. script.
The trace backend is chosen at configure time and only one trace backend can The trace backends are chosen at configure time:
be built into the binary:
./configure --trace-backends=simple ./configure --enable-trace-backends=simple
For a list of supported trace backends, try ./configure --help or see below. For a list of supported trace backends, try ./configure --help or see below.
If multiple backends are enabled, the trace is sent to them all.
The following subsections describe the supported trace backends. The following subsections describe the supported trace backends.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment