From: Prerna Saxena <prerna@linux.vnet.ibm.com>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Mahesh <mahesh@linux.vnet.ibm.com>,
Ananth Narayan <ananth@linux.vnet.ibm.com>,
Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: [Qemu-devel] [Tracing][v4 PATCH 2/2] Add documentation for QMP interfaces
Date: Tue, 19 Oct 2010 11:57:50 +0530 [thread overview]
Message-ID: <20101019115750.7ce4a0c7@zephyr> (raw)
In-Reply-To: <20101019114922.66d7c31d@zephyr>
[PATCH 2/2] Add documentation for QMP commands:
- query-trace
- query-trace-events
- query-trace-file.
Signed-off-by: Prerna Saxena <prerna@linux.vnet.ibm.com>
---
qmp-commands.hx | 94 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 94 insertions(+), 0 deletions(-)
diff --git a/qmp-commands.hx b/qmp-commands.hx
index 793cf1c..bc79b55 100644
--- a/qmp-commands.hx
+++ b/qmp-commands.hx
@@ -1539,3 +1539,97 @@ Example:
EQMP
+SQMP
+query-trace
+-------------
+
+Show contents of trace buffer.
+
+Returns a set of json-objects containing the following data:
+
+- "event": Event ID for the trace-event(json-int)
+- "timestamp": trace timestamp (json-int)
+- "arg1 .. arg6": Arguments logged by the trace-event (json-int)
+
+Example:
+
+-> { "execute": "query-trace" }
+<- {
+ "return":{
+ "event": 22,
+ "timestamp": 129456235912365,
+ "arg1": 886
+ "arg2": 80,
+ "arg3": 0,
+ "arg4": 0,
+ "arg5": 0,
+ "arg6": 0,
+ },
+ {
+ "event": 22,
+ "timestamp": 129456235973407,
+ "arg1": 886,
+ "arg2": 80,
+ "arg3": 0,
+ "arg4": 0,
+ "arg5": 0,
+ "arg6": 0
+ },
+ ...
+ }
+
+EQMP
+
+SQMP
+query-trace-events
+------------------
+
+Show all available trace-events & their state.
+
+Returns a set of json-objects containing the following data:
+
+- "name": Name of Trace-event (json-string)
+- "event-id": Event ID of Trace-event (json-int)
+- "state": State of trace-event [ '0': inactive; '1':active ] (json-int)
+
+Example:
+
+-> { "execute": "query-trace-events" }
+<- {
+ "return":{
+ "name": "qemu_malloc",
+ "event-id": 0
+ "state": 0,
+ },
+ {
+ "name": "qemu_realloc",
+ "event-id": 1,
+ "state": 0
+ },
+ ...
+ }
+
+EQMP
+
+SQMP
+query-trace-file
+----------------
+
+Display currently set trace file name and its status.
+
+Returns a set of json-objects containing the following data:
+
+- "trace-file": Name of Trace-file (json-string)
+- "status": State of trace-event [ '0': disabled; '1':enabled ] (json-int)
+
+Example:
+
+-> { "execute": "query-trace-file" }
+<- {
+ "return":{
+ "trace-file": "trace-26609",
+ "status": 1
+ }
+ }
+
+EQMP
--
1.7.2.2
--
Prerna Saxena
Linux Technology Centre,
IBM Systems and Technology Lab,
Bangalore, India
next prev parent reply other threads:[~2010-10-19 6:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 6:19 [Qemu-devel] [Tracing][v4 PATCH 0/2] QMP Query interfaces for tracing Prerna Saxena
2010-10-19 6:25 ` [Qemu-devel] [Tracing][v4 PATCH 1/2] Introduce QMP interfaces Prerna Saxena
2010-10-19 9:12 ` [Qemu-devel] " Stefan Hajnoczi
2010-10-19 6:27 ` Prerna Saxena [this message]
2010-10-19 9:12 ` [Qemu-devel] Re: [Tracing][v4 PATCH 2/2] Add documentation for " Stefan Hajnoczi
2010-10-19 12:44 ` [Qemu-devel] " Prerna Saxena
2010-10-20 19:17 ` [Qemu-devel] " Luiz Capitulino
2010-10-21 6:51 ` Prerna Saxena
2010-10-21 12:12 ` Luiz Capitulino
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=20101019115750.7ce4a0c7@zephyr \
--to=prerna@linux.vnet.ibm.com \
--cc=ananth@linux.vnet.ibm.com \
--cc=lcapitulino@redhat.com \
--cc=mahesh@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
/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).