From: Harsh Bora <harsh@linux.vnet.ibm.com>
To: "Lluís Vilanova" <vilanova@ac.upc.edu>
Cc: aneesh.kumar@linux.vnet.ibm.com, stefanha@linux.vnet.ibm.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH 0/4] simpletrace : support var num/size of args, strings.
Date: Wed, 04 Jan 2012 11:43:31 +0530 [thread overview]
Message-ID: <4F03EE0B.706@linux.vnet.ibm.com> (raw)
In-Reply-To: <877h1a5kun.fsf@ginnungagap.bsc.es>
On 01/02/2012 06:20 PM, Lluís Vilanova wrote:
> Harsh Prateek Bora writes:
>
>> Converting tracetool.sh to tracetool.py
>
> Excellent! I was thinking about switching the script language to python, but
> wasn't sure if python was an acceptable build dependency for the project.
Thanks, Python appears to become mandatory requirement soon as per
http://lists.gnu.org/archive/html/qemu-devel/2012-01/msg00169.html
>
> I was modifying the bash tracetool to add a tracing layer more amenable to
> instrumentation (together with the API that Avi suggested for 3rd party tracing
> tools to interact with QEMU).
>
> It currently looks like:
>
> * trace.h (includes trace-backend.h)
> -> backend={no instrumentation, static instr, dynamic instr (dlopen)}
> * trace-backend.h
> -> backend={nop,stderr,simple,dtrace,...}
>
> And similarly for TCG tracing.
>
> What I'd like to know is if I can switch right away into this new script to
> finish these changes (and avoid doing the work twice).
I guess yes, however this patch still needs to be updated for code
generation for other tracing backends.
- Harsh
>
>
> Lluis
>
prev parent reply other threads:[~2012-01-04 6:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-02 6:50 [Qemu-devel] [RFC PATCH 0/4] simpletrace : support var num/size of args, strings Harsh Prateek Bora
2012-01-02 6:50 ` [Qemu-devel] [RFC PATCH 1/4] Converting tracetool.sh to tracetool.py Harsh Prateek Bora
2012-01-02 6:50 ` [Qemu-devel] [RFC PATCH 2/4] Makefile and configure changes for tracetool.py Harsh Prateek Bora
2012-01-02 6:50 ` [Qemu-devel] [RFC PATCH 3/4] simpletrace-v2: Handle variable number/size of elements per trace record Harsh Prateek Bora
2012-01-02 6:50 ` [Qemu-devel] [PATCH 4/4] simpletrace.py: Simpletrace v2 tracelog reader script Harsh Prateek Bora
2012-01-02 7:03 ` Harsh Bora
2012-01-02 6:50 ` [Qemu-devel] [RFC PATCH 4/4] simpletrace.py: updated log reader script to handle new log format Harsh Prateek Bora
2012-01-02 12:50 ` [Qemu-devel] [RFC PATCH 0/4] simpletrace : support var num/size of args, strings Lluís Vilanova
2012-01-04 6:13 ` Harsh Bora [this message]
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=4F03EE0B.706@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 \
--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).