qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mohamad Gebai <mohamad.gebai@polymtl.ca>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH v2 0/3] Fix UST backend for LTTng 2.x
Date: Mon, 14 Oct 2013 13:05:14 -0400	[thread overview]
Message-ID: <525C244A.6060503@polymtl.ca> (raw)
In-Reply-To: <p1bo318dhj.fsf@linaro.org>

Sorry for the delay, just submitted the updated documentation.

Thanks,
Mohamad

On 13-10-07 08:36 AM, Alex Bennée wrote:
> mohamad.gebai@gmail.com writes:
>
>> Version 2
>>
>> * Fix tracepoint generation error in first version.
>> * Avoid warnings and errors specific to LTTng ust 2.0.
>> * If using LTTng ust 2.0, we can't avoid getting warnings because of the
>>    --warn-common option given to the linker. This is fixed in more recent
>>    versions of LTTng ust.
> Looking good. Builds for me now although I need to do some reading to
> actually test it out. One omission is docs/tracing.txt gives examples
> for the other tracing backend but just refers to "UST utilities should
> be used to list, enable/disable, and dump traces.". Perhaps a few simple
> examples could be added to the document so people can at least confirm
> everything is working as it should be. Otherwise I'm happy.
>
> Reviewed-by: Alex Bennée <alex@bennee.com>
>
>> Mohamad
>>
>> Mohamad Gebai (3):
>>    Fix configure script for LTTng 2.x
>>    Modified the tracetool framework for LTTng 2.x.
>>    Adapt Makefiles to the new LTTng ust interface.
>>
>>   Makefile                                 |    5 ++
>>   configure                                |    9 ++--
>>   scripts/tracetool/backend/events.py      |   44 ++++++++++++++++
>>   scripts/tracetool/backend/ust.py         |   82 ++++++------------------------
>>   scripts/tracetool/format/ust_events_c.py |   30 +++++++++++
>>   scripts/tracetool/format/ust_events_h.py |   57 +++++++++++++++++++++
>>   trace/Makefile.objs                      |   29 ++++++++++-
>>   7 files changed, 183 insertions(+), 73 deletions(-)
>>   create mode 100644 scripts/tracetool/format/ust_events_c.py
>>   create mode 100644 scripts/tracetool/format/ust_events_h.py
>

  reply	other threads:[~2013-10-14 17:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-04 19:07 [Qemu-devel] [RFC PATCH v2 0/3] Fix UST backend for LTTng 2.x Mohamad Gebai
2013-10-04 19:07 ` [Qemu-devel] [RFC PATCH v2 1/3] Fix configure script " Mohamad Gebai
2013-10-04 19:07 ` [Qemu-devel] [RFC PATCH v2 2/3] Modified the tracetool framework " Mohamad Gebai
2013-10-04 19:07 ` [Qemu-devel] [RFC PATCH v2 3/3] Adapt Makefiles to the new LTTng ust interface Mohamad Gebai
2013-10-07 12:36 ` [Qemu-devel] [RFC PATCH v2 0/3] Fix UST backend for LTTng 2.x Alex Bennée
2013-10-14 17:05   ` Mohamad Gebai [this message]
2013-10-15 11:48     ` 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=525C244A.6060503@polymtl.ca \
    --to=mohamad.gebai@polymtl.ca \
    --cc=alex.bennee@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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).