All of lore.kernel.org
 help / color / mirror / Atom feed
From: Genevieve Bastien <gbastien+lttng@versatic.net>
To: lttng-dev@lists.lttng.org
Subject: Re: CTF -> Chrome Trace Event
Date: Wed, 1 Nov 2017 11:57:08 -0400	[thread overview]
Message-ID: <9ea71b68-d929-b284-afff-8109df8225d4__20353.4350767315$1509553804$gmane$org@versatic.net> (raw)
In-Reply-To: <CADwgpi9pwMp_wWAEjtpvcGEx6R2wifaHABZjgmQD9QUGufa1AA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1278 bytes --]

Hi Alok,


I don't know about anyone converting CTF to Catapult trace events, (it
would probably be rather straightforward to do with babeltrace 2 if you
know how to translate the events correctly) but in the Trace Compass
Incubator, we do have support for the trace-event format, so that Trace
Compass can read both CTF and trace-event traces.


See here [1] for instructions to install Incubator features and install
the "Trace Compass TraceEvent Parser" feature. You'll get some of the
catapult analyses with it.


[1]
http://versatic.net/tracecompass/incubator/2017/09/13/introducing-tracecompass-incubator.html


Cheers,

Geneviève


On 2017-10-31 07:33 PM, Alok Priyadarshi wrote:
> Hello,
>
> I am considering using lttng in my current project. We also like
> Catapult <https://github.com/catapult-project/catapult> trace viewer
> used by chrome://tracing.
>
> I am wondering if someone has tried translating CTF tracepoints into
> Catapult trace events, whose format is described
> here: https://docs.google.com/document/d/1CvAClvFfyA5R-PhYUmn5OOQtYMH4h6I0nSsKchNAySU/preview
>
> Thanks in advance.
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev


[-- Attachment #1.2: Type: text/html, Size: 2693 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

       reply	other threads:[~2017-11-01 16:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CADwgpi9pwMp_wWAEjtpvcGEx6R2wifaHABZjgmQD9QUGufa1AA@mail.gmail.com>
2017-11-01 15:57 ` Genevieve Bastien [this message]
2017-10-31 23:33 CTF -> Chrome Trace Event Alok Priyadarshi

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='9ea71b68-d929-b284-afff-8109df8225d4__20353.4350767315$1509553804$gmane$org@versatic.net' \
    --to=gbastien+lttng@versatic.net \
    --cc=lttng-dev@lists.lttng.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.