From: Harsh Prateek Bora <harsh@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: aneesh.kumar@linux.vnet.ibm.com, mathieu.desnoyers@efficios.com,
vilanova@ac.upc.edu, stefanha@linux.vnet.ibm.com
Subject: [Qemu-devel] [RFC PATCH v3 0/3] simpletrace : support var num of args and strings.
Date: Tue, 10 Jan 2012 16:29:36 +0530 [thread overview]
Message-ID: <1326193179-19677-1-git-send-email-harsh@linux.vnet.ibm.com> (raw)
Existing simple trace can log upto 6 args per trace event and does not
support strings in trace record format. Introducing new trace format as
discussed earlier on list to support variable number/size of arguments.
(Ref: http://lists.gnu.org/archive/html/qemu-devel/2011-11/msg03426.html)
Basic testing of new tracelog format is successful. Stress testing not yet done.
Apply patches, then run:
make distclean
./configure with --enable-trace-backend=simple
make
sudo make install
Sample tracelog showing strings support:
[harsh@harshbora v9fs]$ scripts/simpletrace.py trace-events trace-23261
v9fs_version 0.000 tag=65535 id=100 msize=8192 version=9P2000.L
v9fs_version_return 17.530 tag=65535 id=100 msize=8192 version=9P2000.L
v9fs_attach 180.121 tag=1 id=104 fid=0 afid=18446744073709551615
uname=nobody aname=
Note: Other backends are only compile tested.
Version History:
v3:
- Added support for LTTng ust trace backend in tracetool.py
v2:
- Updated tracetool.py to support nop, stderr, dtrace backend
v1:
- Working protoype with tracetool.py converted only for simpletrace backend
Harsh Prateek Bora (3):
Converting tracetool.sh to tracetool.py
simpletrace-v2: Handle variable number/size of elements per trace
record.
simpletrace.py: updated log reader script to handle new log format
Makefile.objs | 6 +-
Makefile.target | 10 +-
configure | 7 +-
monitor.c | 2 +-
scripts/simpletrace.py | 109 ++++++++-
scripts/tracetool | 643 ------------------------------------------------
scripts/tracetool.py | 585 +++++++++++++++++++++++++++++++++++++++++++
trace/simple.c | 178 +++++---------
trace/simple.h | 31 ++-
9 files changed, 783 insertions(+), 788 deletions(-)
delete mode 100755 scripts/tracetool
create mode 100755 scripts/tracetool.py
next reply other threads:[~2012-01-10 10:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 10:59 Harsh Prateek Bora [this message]
2012-01-10 10:59 ` [Qemu-devel] [RFC PATCH v3 1/3] Converting tracetool.sh to tracetool.py Harsh Prateek Bora
2012-01-10 14:50 ` Stefan Hajnoczi
2012-01-11 6:25 ` Harsh Bora
2012-01-11 10:03 ` Stefan Hajnoczi
2012-01-10 21:45 ` Lluís Vilanova
2012-01-11 17:14 ` Stefan Hajnoczi
2012-01-10 22:51 ` Lluís Vilanova
2012-01-11 6:38 ` Harsh Bora
2012-01-11 8:46 ` Harsh Bora
2012-01-11 10:50 ` Stefan Hajnoczi
2012-01-12 9:33 ` Stefan Hajnoczi
2012-01-11 10:07 ` Stefan Hajnoczi
2012-01-10 10:59 ` [Qemu-devel] [RFC PATCH v3 2/3] simpletrace-v2: Handle variable number/size of elements per trace record Harsh Prateek Bora
2012-01-10 16:41 ` Stefan Hajnoczi
2012-01-18 9:14 ` Harsh Bora
2012-01-18 10:31 ` Stefan Hajnoczi
2012-01-18 10:41 ` Harsh Bora
2012-01-18 10:52 ` Harsh Bora
2012-01-18 10:59 ` Stefan Hajnoczi
2012-01-18 11:09 ` Harsh Bora
2012-01-10 10:59 ` [Qemu-devel] [RFC PATCH v3 3/3] simpletrace.py: updated log reader script to handle new log format Harsh Prateek Bora
2012-01-11 12:30 ` Stefan Hajnoczi
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=1326193179-19677-1-git-send-email-harsh@linux.vnet.ibm.com \
--to=harsh@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
--cc=vilanova@ac.upc.edu \
/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).