qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Harsh Bora <harsh@linux.vnet.ibm.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: vilanova@ac.upc.edu, mathieu.desnoyers@efficios.com,
	qemu-devel@nongnu.org, stefanha@linux.vnet.ibm.com,
	aneesh.kumar@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [RFC PATCH v2 1/4] Converting tracetool.sh to tracetool.py
Date: Tue, 10 Jan 2012 11:42:54 +0530	[thread overview]
Message-ID: <4F0BD6E6.4030001@linux.vnet.ibm.com> (raw)
In-Reply-To: <4F0B56BF.20200@suse.de>

On 01/10/2012 02:36 AM, Andreas Färber wrote:
> Am 09.01.2012 16:46, schrieb Harsh Prateek Bora:
>> Note: Upstream Qemu have build issues with LTTng ust backend, as the trace
>> event APIs are not yet stable in ust and therefore ust backend is not
>> supported in this script as of now. Once the ust API stablises, this script
>> can be updated for ust backend also.
>>
>> Signed-off-by: Harsh Prateek Bora<harsh@linux.vnet.ibm.com>
>> ---
>>   scripts/tracetool    |  643 --------------------------------------------------
>>   scripts/tracetool.py |  505 +++++++++++++++++++++++++++++++++++++++
>>   2 files changed, 505 insertions(+), 643 deletions(-)
>>   delete mode 100755 scripts/tracetool
>>   create mode 100755 scripts/tracetool.py
>
> This will break the build. You need to squash 2/4 into this one.

Yes, 2/4 will be squashed with it.

>
> What does "ust backend is not supported" mean? Did you leave it out
> completely, or did not test it, or tested it and it's not working?

Please see discussion on 0/4 patch thread. Existing tracetool needs a 
fix for ust, and I was not sure about the fix, therefore not converted yet.

- Harsh

>
> Andreas
>

  reply	other threads:[~2012-01-10  6:14 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 [this message]
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 ` [Qemu-devel] [RFC PATCH v2 0/4] simpletrace : support var num of args and strings Mathieu Desnoyers
2012-01-09 19:20   ` 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=4F0BD6E6.4030001@linux.vnet.ibm.com \
    --to=harsh@linux.vnet.ibm.com \
    --cc=afaerber@suse.de \
    --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).