From: Harsh Prateek Bora <harsh@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: stefanha@gmail.com, vilanova@ac.upc.edu, aneesh.kumar@linux.vnet.ibm.com
Subject: [Qemu-devel] [RFC PATCH v5 00/14] Tracing Improvements, Simpletrace v2
Date: Thu, 1 Mar 2012 18:55:26 +0530 [thread overview]
Message-ID: <1330608340-9515-1-git-send-email-harsh@linux.vnet.ibm.com> (raw)
This patchset introduces 2 major updates:
1) Tracetool Improvements (Conversion from shell script to python)
2) Simpletrace v2 log format (Support for variable args, strings)
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.
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:
v5:
- trace/simple.c: Introduced new struct TraceRecordHeader for log header
consistency
- Addressed Stefan's review comments for scripts/simpletrace.py
v4:
- Addressed Stefan's review comments for tracetool, trace/simple.*
- Adressed Fast producer, Slow consumer problem
- Isolated tracetool python conversion patch from simpletrace v2 changes.
- Included improvements and fixes from Lluis Vilanova
TODO: Update simpletrace.py for simpletrace v2 log format.
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 (4):
Converting tracetool.sh to tracetool.py
monitor: remove unused do_info_trace
Simpletrace v2: Handle var num of args, strings.
scripts/simpltrace.py changes
Lluís Vilanova (10):
trace: [tracetool] Do not rebuild event list in backend code
trace: [tracetool] Simplify event line parsing
trace: [tracetool] Do not precompute the event number
trace: [tracetool] Add support for event properties
trace: [tracetool] Process the "disable" event property
trace: [tracetool] Rewrite event argument parsing
trace: [tracetool] Make format-specific code optional with access to
events
trace: [tracetool] Automatically establish available backends and
formats
trace: Provide a per-event status define for conditional compilation
trace: [tracetool] Add error-reporting functions
Makefile.objs | 6 +-
Makefile.target | 13 +-
configure | 7 +-
docs/tracing.txt | 50 ++++-
monitor.c | 16 --
scripts/simpletrace.py | 139 ++++++++----
scripts/tracetool | 643 ------------------------------------------------
scripts/tracetool.py | 635 +++++++++++++++++++++++++++++++++++++++++++++++
trace/simple.c | 238 ++++++++++--------
trace/simple.h | 38 +++-
10 files changed, 954 insertions(+), 831 deletions(-)
delete mode 100755 scripts/tracetool
create mode 100755 scripts/tracetool.py
next reply other threads:[~2012-03-01 13:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 13:25 Harsh Prateek Bora [this message]
2012-03-01 13:25 ` [Qemu-devel] [RFC PATCH v5 01/14] Converting tracetool.sh to tracetool.py Harsh Prateek Bora
2012-03-01 13:25 ` [Qemu-devel] [RFC PATCH v5 02/14] trace: [tracetool] Do not rebuild event list in backend code Harsh Prateek Bora
2012-03-01 13:25 ` [Qemu-devel] [RFC PATCH v5 03/14] trace: [tracetool] Simplify event line parsing Harsh Prateek Bora
2012-03-01 13:25 ` [Qemu-devel] [RFC PATCH v5 04/14] trace: [tracetool] Do not precompute the event number Harsh Prateek Bora
2012-03-01 13:25 ` [Qemu-devel] [RFC PATCH v5 05/14] trace: [tracetool] Add support for event properties Harsh Prateek Bora
2012-03-01 13:25 ` [Qemu-devel] [RFC PATCH v5 06/14] trace: [tracetool] Process the "disable" event property Harsh Prateek Bora
2012-03-01 13:25 ` [Qemu-devel] [RFC PATCH v5 07/14] trace: [tracetool] Rewrite event argument parsing Harsh Prateek Bora
2012-03-01 13:25 ` [Qemu-devel] [RFC PATCH v5 08/14] trace: [tracetool] Make format-specific code optional with access to events Harsh Prateek Bora
2012-03-01 13:25 ` [Qemu-devel] [RFC PATCH v5 09/14] trace: [tracetool] Automatically establish available backends and formats Harsh Prateek Bora
2012-03-01 13:25 ` [Qemu-devel] [RFC PATCH v5 10/14] trace: Provide a per-event status define for conditional compilation Harsh Prateek Bora
2012-03-12 15:25 ` Lluís Vilanova
2012-03-14 5:25 ` Harsh Bora
2012-03-01 13:25 ` [Qemu-devel] [RFC PATCH v5 11/14] trace: [tracetool] Add error-reporting functions Harsh Prateek Bora
2012-03-01 13:25 ` [Qemu-devel] [RFC PATCH v5 12/14] monitor: remove unused do_info_trace Harsh Prateek Bora
2012-03-01 13:25 ` [Qemu-devel] [RFC PATCH v5 13/14] Simpletrace v2: Handle var num of args, strings Harsh Prateek Bora
2012-03-01 13:25 ` [Qemu-devel] [RFC PATCH v5 14/14] scripts/simpltrace.py changes: Support simplettrace v2 Harsh Prateek Bora
2012-03-13 20:11 ` [Qemu-devel] [RFC PATCH v5 00/14] Tracing Improvements, Simpletrace v2 Lluís Vilanova
2012-03-14 5:36 ` Harsh 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=1330608340-9515-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@gmail.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).