From: Harsh Prateek Bora <harsh@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: Harsh Prateek Bora <harsh@linux.vnet.ibm.com>,
aneesh.kumar@linux.vnet.ibm.com, stefanha@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH 0/3] Simpletrace v2: Support multiple args, strings.
Date: Thu, 3 May 2012 23:26:33 +0530 [thread overview]
Message-ID: <1336067796-5730-1-git-send-email-harsh@linux.vnet.ibm.com> (raw)
Existing simpletrace backend allows to trace at max 6 args and does not
support strings. This newer tracelog format gets rid of fixed size records
and therefore allows to trace variable number of args including strings.
Sample trace:
v9fs_version 0.000 tag=0xffff id=0x64 msize=0x2000 version=9P2000.L
v9fs_version_return 6.705 tag=0xffff id=0x64 msize=0x2000 version=9P2000.L
v9fs_attach 174.467 tag=0x1 id=0x68 fid=0x0 afid=0xffffffffffffffff uname=nobody aname=
v9fs_attach_return 4720.454 tag=0x1 id=0x68 type=0xffffffffffffff80 version=0x4f2a4dd0 path=0x220ea6
Harsh Prateek Bora (3):
monitor: remove unused do_info_trace
simpletrace v2: Support var number of args, strings.
Update simpletrace.py to support new v2 log format
monitor.c | 16 ---
scripts/simpletrace.py | 138 ++++++++++++++------
scripts/tracetool/backend/simple.py | 84 +++++++++---
trace/simple.c | 246 ++++++++++++++++++++---------------
trace/simple.h | 39 +++++-
5 files changed, 335 insertions(+), 188 deletions(-)
next reply other threads:[~2012-05-03 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 17:56 Harsh Prateek Bora [this message]
2012-05-03 17:56 ` [Qemu-devel] [PATCH 1/3] monitor: remove unused do_info_trace Harsh Prateek Bora
2012-05-07 13:46 ` Lluís Vilanova
2012-05-08 5:11 ` Harsh Bora
2012-05-03 17:56 ` [Qemu-devel] [PATCH 2/3] simpletrace v2: Support var number of args, strings Harsh Prateek Bora
2012-05-03 17:56 ` [Qemu-devel] [PATCH 3/3] Update simpletrace.py to support new v2 log format Harsh Prateek Bora
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=1336067796-5730-1-git-send-email-harsh@linux.vnet.ibm.com \
--to=harsh@linux.vnet.ibm.com \
--cc=aneesh.kumar@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).