qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
	Prerna Saxena <prerna@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH] trace: Documentation update
Date: Mon,  9 Aug 2010 15:03:28 +0100	[thread overview]
Message-ID: <1281362608-10106-1-git-send-email-stefanha@linux.vnet.ibm.com> (raw)

Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
---
 docs/tracing.txt |   21 ++++++++++++---------
 1 files changed, 12 insertions(+), 9 deletions(-)

diff --git a/docs/tracing.txt b/docs/tracing.txt
index abbae6b..fe3c6ac 100644
--- a/docs/tracing.txt
+++ b/docs/tracing.txt
@@ -18,7 +18,7 @@ for debugging, profiling, and observing execution.
 
 3. Pretty-print the binary trace file:
 
-    ./simpletrace.py trace-events /tmp/trace.log
+    ./simpletrace.py trace-events /tmp/trace-*
 
 == Trace events ==
 
@@ -70,11 +70,11 @@ trace events.
 
 == Trace backends ==
 
-The tracetool script not only automates tedious trace event code generation,
-it also keeps the trace event declarations independent of the trace backend.
-The trace 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 script.
+The tracetool script automates tedious trace event code generation and also
+keeps the trace event declarations independent of the trace backend.  The trace
+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
+script.
 
 The trace backend is chosen at configure time and only one trace backend can
 be built into the binary:
@@ -116,16 +116,19 @@ unless you have specific needs for more advanced backends.
 * trace-event NAME on|off
   Enable/disable a given trace event.
 
+* trace-file on|off|flush|set <path>
+  Enable/disable/flush the trace file or set the trace file name.
+
 ==== Enabling/disabling trace events programmatically ====
 
-The change_trace_event_state() function can be used to enable or disable trace
+The st_change_trace_event_state() function can be used to enable or disable trace
 events at runtime inside QEMU:
 
     #include "trace.h"
     
-    change_trace_event_state("virtio_irq", true); /* enable */
+    st_change_trace_event_state("virtio_irq", true); /* enable */
     [...]
-    change_trace_event_state("virtio_irq", false); /* disable */
+    st_change_trace_event_state("virtio_irq", false); /* disable */
 
 ==== Analyzing trace files ====
 
-- 
1.7.1

                 reply	other threads:[~2010-08-09 14:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1281362608-10106-1-git-send-email-stefanha@linux.vnet.ibm.com \
    --to=stefanha@linux.vnet.ibm.com \
    --cc=prerna@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).