qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mohamad Gebai <mohamad.gebai@gmail.com>
To: qemu-devel@nongnu.org
Cc: Mohamad Gebai <mohamad.gebai@polymtl.ca>
Subject: [Qemu-devel] [RFC PATCH 0/3] Fix UST backend for LTTng 2.x
Date: Mon, 30 Sep 2013 11:04:58 -0400	[thread overview]
Message-ID: <1380553501-20670-1-git-send-email-mohamad.gebai@polymtl.ca> (raw)

These patches fix the UST backend which got broken by LTTng 2.x.

An interesting new feature in LTTng 2.x is that tracepoints now need to belong
to a provider. A provider is a way to group tracepoints in a logical way, for
instance tracepoints that belong to a specific file or subsystem. This would
then allow users to enable all tracepoints of a specific provider at once.

In these patches, only one provider is defined, which is called "ust" (and
tracepoints are defined in generated-ust-provider.h). It would be interesting to
take advantage of this feature in the future, separating tracepoints into
multiple providers. Of course, this would require more modifications as well as
a way to specify to which provider each tracepoint belongs in file trace-events.

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 |   39 ++++++++++++++
 trace/Makefile.objs                      |   29 ++++++++++-
 7 files changed, 165 insertions(+), 73 deletions(-)
 create mode 100644 scripts/tracetool/format/ust_events_c.py
 create mode 100644 scripts/tracetool/format/ust_events_h.py

-- 
1.7.10.4

             reply	other threads:[~2013-09-30 15:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-30 15:04 Mohamad Gebai [this message]
2013-09-30 15:04 ` [Qemu-devel] [RFC PATCH 1/3] Fix configure script for LTTng 2.x Mohamad Gebai
2013-09-30 15:05 ` [Qemu-devel] [RFC PATCH 2/3] Modified the tracetool framework " Mohamad Gebai
2013-09-30 15:05 ` [Qemu-devel] [RFC PATCH 3/3] Adapt Makefiles to the new LTTng ust interface Mohamad Gebai
2013-10-01 10:04 ` [Qemu-devel] [RFC PATCH 0/3] Fix UST backend for LTTng 2.x Alex Bennée

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=1380553501-20670-1-git-send-email-mohamad.gebai@polymtl.ca \
    --to=mohamad.gebai@gmail.com \
    --cc=mohamad.gebai@polymtl.ca \
    --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).