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: Dr. David Alan Gilbert <dgilbert@redhat.com>
Message-id: 1412691161-31785-1-git-send-email-dgilbert@redhat.com
Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
This commit is contained in:
Dr. David Alan Gilbert 2014-10-07 15:12:41 +01:00 committed by Stefan Hajnoczi
parent 1aba4be97e
commit b73e8bd414

View File

@ -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.