From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Harsh Prateek Bora <harsh@linux.vnet.ibm.com>
Cc: aneesh.kumar@linux.vnet.ibm.com, lttng-dev@lists.lttng.org,
qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com,
vilanova@ac.upc.edu
Subject: Re: [Qemu-devel] [RFC PATCH v2 0/4] simpletrace : support var num of args and strings.
Date: Mon, 9 Jan 2012 11:01:05 -0500 [thread overview]
Message-ID: <20120109160105.GA2444@Krystal> (raw)
In-Reply-To: <1326123980-6038-1-git-send-email-harsh@linux.vnet.ibm.com>
* Harsh Prateek Bora (harsh@linux.vnet.ibm.com) wrote:
> 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 this patch 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: LTTng ust backend is broken in upstream qemu, therefore tracetool.py
> doesnt support ust backend as of now. IIUC, ust's trace event APIs are under
> development and not yet stable.
Hi,
FYI, the LTTng-UST TRACEPOINT_EVENT API is very much stable as of now.
Even though we are still in LTTng-UST 2.0 prereleases, the fact that we
started the round of discussions on this API last summer makes us
confident that from this point on we should not have to change it.
Moreover, I would like to know if the old UST 0.x (0.16 is the latest)
is broken wrt qemu, or if this is just for LTTng-2.0 UST support ?
UST 0.x instrumentation is not supposed to have broken wrt qemu.
Best regards,
Mathieu
>
> Version History:
>
> 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
> Makefile and configure changes for 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 | 4 +-
> monitor.c | 2 +-
> scripts/simpletrace.py | 110 ++++++++++-
> scripts/tracetool.py | 505 ++++++++++++++++++++++++++++++++++++++++++++++++
> trace/simple.c | 178 ++++++-----------
> trace/simple.h | 31 +++-
> 8 files changed, 702 insertions(+), 144 deletions(-)
> create mode 100755 scripts/tracetool.py
>
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2012-01-09 16:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 15:46 [Qemu-devel] [RFC PATCH v2 0/4] simpletrace : support var num of args and strings Harsh Prateek Bora
2012-01-09 15:46 ` [Qemu-devel] [RFC PATCH v2 1/4] Converting tracetool.sh to tracetool.py Harsh Prateek Bora
2012-01-09 21:06 ` Andreas Färber
2012-01-10 6:12 ` Harsh Bora
2012-01-09 15:46 ` [Qemu-devel] [RFC PATCH v2 2/4] Makefile and configure changes for tracetool.py Harsh Prateek Bora
2012-01-09 15:46 ` [Qemu-devel] [RFC PATCH v2 3/4] simpletrace-v2: Handle variable number/size of elements per trace record Harsh Prateek Bora
2012-01-09 15:46 ` [Qemu-devel] [RFC PATCH v2 4/4] simpletrace.py: updated log reader script to handle new log format Harsh Prateek Bora
2012-01-09 16:01 ` Mathieu Desnoyers [this message]
2012-01-09 19:20 ` [Qemu-devel] [RFC PATCH v2 0/4] simpletrace : support var num of args and strings Harsh Bora
2012-01-10 0:14 ` Mathieu Desnoyers
2012-01-10 6:54 ` Harsh Bora
2012-01-10 7:17 ` [Qemu-devel] [lttng-dev] " Mathieu Desnoyers
2012-01-10 9:06 ` Harsh Bora
2012-01-10 10:44 ` Harsh Bora
2012-01-10 14:18 ` Mathieu Desnoyers
2012-01-10 14:58 ` Stefan Hajnoczi
2012-01-10 17:29 ` Mathieu Desnoyers
2012-01-11 9: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=20120109160105.GA2444@Krystal \
--to=mathieu.desnoyers@efficios.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=harsh@linux.vnet.ibm.com \
--cc=lttng-dev@lists.lttng.org \
--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).