OpenE2K
/
qemu-e2k
13
4
Fork 0
Code Issues 4 Pull Requests Projects 2 Releases Activity

-----BEGIN PGP SIGNATURE----- 

iQEcBAABAgAGBQJYIhapAAoJEJykq7OBq3PIkBoH/jWgy1B9/SblX8Ed1qeA+SCV
 pMUYOSv2ldNBd0GPVFlhlQXslBv/CJtXEvZyMY2uwgP/k2hYRQga2OsF7XPRYVLE
 2jzTRFB98zNBcIL1yCrJukNQtNCLZCTZTmDZ4L6FmkwcD4fVPqZPgSM4G50aHq8/
 EUrfidiyEa/wB6N5LcIWX4/v3CPDj9xF94qKtUFa4I+wSaR8n6qZNUTw1YdD/P2D
 TIMAlaB4YhpObSiqAE0VWXBEZ8MXjNF5MNRh1Oi8bWaCbkvCcI8iXUAO/ZGlKm2H
 4uZBfrqJpGfZPRy7S8Qges/2Xk2P6d7bUSfYdRmPnsUA2b5UtgxdRHIMUKtl9C8=
 =sxVN
 -----END PGP SIGNATURE-----

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: Stefan Hajnoczi <stefanha@redhat.com>
This commit is contained in:
Stefan Hajnoczi 2016-11-09 12:44:16 +00:00
parent f70073df4a 3b0fc80dd8
commit 9b4b035026
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
docs/tracing.txt
View File

@ -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.
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.
=== Nop ===
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
performance penalty.
can optimize out trace events completely. This imposes no performance
penalty.
Note that regardless of the selected trace backend, events with the "disable"
property will be generated with the "nop" backend.