Hi,
I'm a developer for the Trace Compass tool (see links [3], [4] in Jiri's
email). I can confirm that the generated CTF can be read correctly by
our tool, which enables many views and analyses (Control Flow, CPU usage
view, etc.) that were previously only available for LTTng traces.
Some o
On 2015-01-15 03:57 PM, Alexandre Montplaisir wrote:
Hi,
I'm a developer for the Trace Compass tool (see links [3], [4] in
Jiri's email). I can confirm that the generated CTF can be read
correctly by our tool, which enables many views and analyses (Control
Flow, CPU usage view,
On 2015-04-09 05:46 AM, Jiri Olsa wrote:
On Thu, Apr 09, 2015 at 04:19:20PM +0800, He Kuang wrote:
Hi, jirka
On 2015/4/9 1:45, Jiri Olsa wrote:
On Wed, Apr 08, 2015 at 12:49:19PM +0800, He Kuang wrote:
Show message when errors occurred during ctf conversion setup.
Before this patch:
$ ./pe
On 08/21/2014 12:58 PM, Jiri Olsa wrote:
hum, I've got nothing from babeltrace:
[jolsa@krava ~]$ su
Password:
[root@krava jolsa]# lttng create perf
Spawning a session daemon
Session perf created.
Traces will be written in /root/lttng-traces/perf-20140821-184956
[root@krava jolsa]# lttng add-con
On 08/20/2014 05:28 AM, Jiri Olsa wrote:
ok, easy enough ;-) so I'm guessing this governs the expected
CTF layout for event/stream headers/contexts, right?
Correct, if the domain is "kernel" we then assume that the rest of the
trace contains the expected elements of a kernel trace.
Of cours
On 11/05/2014 01:50 PM, Sebastian Andrzej Siewior wrote:
[...]
If the trace events from both LTTng and perf represent the same thing
(and I assume they should, since they come from the same tracepoints,
right?), then we could just add a wrapper on the viewer side to
decide which event/field nam
Hi Mathieu,
On 11/05/2014 06:21 PM, Mathieu Desnoyers wrote:
[...]
The cpu_id field change will be addressed soon on our side.
Now, the remaining things:
The "domain = kernel" thingy (or another identifier if desired) is
something we could add.
Unless the event data is exactly the same, it wo
Hi Sebastian,
On 11/03/2014 06:58 PM, Sebastian Andrzej Siewior wrote:
[...]
I did on the linux side:
|perf record \
| -e sched:sched_switch \
| -a
This gave me perf.data trace. No with the new extension I converted it
into CTF data stream (perf data convert -i perf.data --to-ctf ctf) and
impo
On 11/09/2014 08:31 PM, Alexandre Montplaisir wrote:
On 2014-11-05 10:25 PM, Alexandre Montplaisir wrote:
But if you could for example tell me the perf equivalents of all the
strings in that file, I could hack together such wrapper. With that,
in theory, perf traces should behave exactly
On 11/27/2014 10:43 AM, Jiri Olsa wrote:
On Wed, Nov 12, 2014 at 05:14:45PM -0500, Alexandre Montplaisir wrote:
Testing welcome!
hi,
any other way besides compiling eclipse to test this? For pure mortals
with Fedora eclipse rpm.. ;-)
If you already have an Eclipse installation, you can use
On 2014-11-26 12:37 PM, Sebastian Andrzej Siewior wrote:
* Alexandre Montplaisir | 2014-11-12 17:14:45 [-0500]:
Just a quick note, this branch is now merged to master. So anyone who
pulls the code from the master branch at
git://git.eclipse.org/gitroot/tracecompass/org.eclipse.tracecompass.git
11 matches
Mail list logo
