On 08/05/2014 04:51 PM, Jérémie Galarneau wrote:
> FYI, I have made the changes and they are now upstream in Babeltrace as of
Thanks you. Let me wire that up…
>
> Regards,
> Jérémie
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On Fri, Jul 18, 2014 at 8:34 AM, Sebastian Andrzej Siewior
wrote:
> On 07/14/2014 04:15 PM, Jiri Olsa wrote:
>>> for more data while reading the "events" traces. The latter will be
>>> probably replaced by https://lkml.org/lkml/2014/4/3/217.
>>> Babeltrace needs only
>>> "ctf-writer: Add suppo
On 07/24/2014 04:46 PM, Jiri Olsa wrote:
> hi,
Hi,
> I made some changes over your branch:
> git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
> perf/ctf_convert
>
> following patches:
> (needs to be prettyfied, but hopefuly works and ilustrate the point)
> perf tools: Iterate b
On Tue, Jul 22, 2014 at 03:31:28PM +0200, Sebastian Andrzej Siewior wrote:
SNIP
>
> So the strings look good now. I also renamed "pid" to "common_pid" because
>
> [06:37:09.885385418] (+0.017541187) sched:sched_wakeup: { cpu_id = 0 },
> { common_pid = 179, common_tid = 179, common_comm = ":179"
On 07/22/2014 01:31 PM, Sebastian Andrzej Siewior wrote:
>> [jolsa@krava perf]$ LD_LIBRARY_PATH=/opt/libbabeltrace/lib
>> /opt/libbabeltrace/bin/babeltrace ./ctf-data/
>>
>> [04:41:11.445378840] (+?.?) sched:sched_switch: { }, { pid = 5782,
>> comm = "ls", prev_comm = [ [0] = "ls", [1] =
On 07/22/2014 01:25 PM, Jiri Olsa wrote:
> I've got it running... make LIBBABELTRACE_DIR=/opt/libbabeltrace/ ugh ;-)
>
> [jolsa@krava perf]$ LD_LIBRARY_PATH=/opt/libbabeltrace/lib
> /opt/libbabeltrace/bin/babeltrace ./ctf-data/
>
> [04:41:11.445378840] (+?.?) sched:sched_switch: { }, {
On Tue, Jul 22, 2014 at 08:58:17AM +0200, Sebastian Andrzej Siewior wrote:
> On 07/21/2014 08:35 PM, Jiri Olsa wrote:
> > On Mon, Jul 21, 2014 at 07:11:51PM +0200, Sebastian Andrzej Siewior wrote:
> >
> > heya,
> > I've got following build error:
> >
> > CC util/data-bt.o
> > util/data-bt
On 07/21/2014 08:35 PM, Jiri Olsa wrote:
> On Mon, Jul 21, 2014 at 07:11:51PM +0200, Sebastian Andrzej Siewior wrote:
>
> heya,
> I've got following build error:
>
> CC util/data-bt.o
> util/data-bt.c: In function ‘add_event_tracepoint_value’:
> util/data-bt.c:293:3: error: implicit decla
On Mon, Jul 21, 2014 at 07:11:51PM +0200, Sebastian Andrzej Siewior wrote:
SNIP
> I have the following now:
>
> |$ ../perf data convert -i perf.data.backup --to-ctf ctf-out-backup &&
> babeltrace ctf-out-backup
> |[11:01:45.468071953] (+?.?) raw_syscalls:sys_enter: { cpu_id = 0 },
> {
* Jiri Olsa | 2014-07-14 16:15:33 [+0200]:
>I made similar effort in C:
>
>---
>I made some *VERY* early perf convert example, mostly to try the ctf-writer
>interface.. you can check in here:
> https://git.kernel.org/cgit/linux/kernel/git/jolsa/perf.git/log/?h=perf/ctf_2
>
>It's able to convert s
- Original Message -
> From: "Sebastian Andrzej Siewior"
> To: "Jiri Olsa"
> Cc: linux-kernel@vger.kernel.org, lttng-...@lists.lttng.org, "Mathieu
> Desnoyers" ,
> a...@kernel.org, "namhyung kim" , tzanu...@gmail.com
> Sent: Fri
On 07/18/2014 02:34 PM, Sebastian Andrzej Siewior wrote:
>> I made similar effort in C:
>>
>> ---
>> I made some *VERY* early perf convert example, mostly to try the ctf-writer
>> interface.. you can check in here:
>>
>> https://git.kernel.org/cgit/linux/kernel/git/jolsa/perf.git/log/?h=perf/ctf
On 07/14/2014 04:15 PM, Jiri Olsa wrote:
>> for more data while reading the "events" traces. The latter will be
>> probably replaced by https://lkml.org/lkml/2014/4/3/217.
>> Babeltrace needs only
>> "ctf-writer: Add support for the cpu_id field"
>> https://www.mail-archive.com/lttng-dev@li
On Tue, Jun 03, 2014 at 06:36:40PM +0200, Sebastian Andrzej Siewior wrote:
> I've been playing with python bindings of perf and babeltrace and came
> up with a way to covert the perf trace into the CTF format. It supports
> both ftrace events (perf record -e raw_syscalls:* w) and perf counters
> (p
I've been playing with python bindings of perf and babeltrace and came
up with a way to covert the perf trace into the CTF format. It supports
both ftrace events (perf record -e raw_syscalls:* w) and perf counters
(perf record -e cache-misses w).
The recorded trace is first read via the "perf scri
15 matches
Mail list logo
