提交 9b4b0350 编写于 作者: S Stefan Hajnoczi

Merge remote-tracking branch 'public/tags/tracing-pull-request' into staging

# gpg: Signature made Tue 08 Nov 2016 06:17:13 PM GMT
# gpg:                using RSA key 0x9CA4ABB381AB73C8
# gpg: Good signature from "Stefan Hajnoczi <stefanha@redhat.com>"
# gpg:                 aka "Stefan Hajnoczi <stefanha@gmail.com>"
# Primary key fingerprint: 8695 A8BF D3F9 7CDA AC35  775A 9CA4 ABB3 81AB 73C8

* public/tags/tracing-pull-request:
  docs/tracing.txt: Update documentation of default backend

Message-id: 1478629053-31709-1-git-send-email-stefanha@redhat.com
Signed-off-by: NStefan Hajnoczi <stefanha@redhat.com>
...@@ -150,13 +150,16 @@ The trace backends are chosen at configure time: ...@@ -150,13 +150,16 @@ The trace backends are chosen at configure time:
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. If multiple backends are enabled, the trace is sent to them all.
If no backends are explicitly selected, configure will default to the
"log" backend.
The following subsections describe the supported trace backends. The following subsections describe the supported trace backends.
=== Nop === === Nop ===
The "nop" backend generates empty trace event functions so that the compiler The "nop" backend generates empty trace event functions so that the compiler
can optimize out trace events completely. This is the default and imposes no can optimize out trace events completely. This imposes no performance
performance penalty. penalty.
Note that regardless of the selected trace backend, events with the "disable" Note that regardless of the selected trace backend, events with the "disable"
property will be generated with the "nop" backend. property will be generated with the "nop" backend.
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册