[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160624124411.GA17642@krava>
Date: Fri, 24 Jun 2016 14:44:11 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Wang Nan <wangnan0@...wei.com>, linux-kernel@...r.kernel.org,
pi3orama@....com, lizefan@...wei.com
Subject: Re: [PATCH v2 0/7] perf ctf: Convert comm, fork and exit events to
CTF
On Fri, Jun 24, 2016 at 09:41:13AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Jun 24, 2016 at 02:29:07PM +0200, Jiri Olsa escreveu:
> > On Fri, Jun 24, 2016 at 11:22:05AM +0000, Wang Nan wrote:
> > > After converting perf.data to CTF, we lost pid-tid-comm mapping. Which
> > > makes inconvience. For example, in perf script output we know which
> > > process issue an event like this:
> > >
> > > compiz 19361 [001] 3275709.313929: raw_syscalls:sys_exit: NR 7 = 0
> > >
> > > After converting to CTF, we only get this:
> > >
> > > [3275709.313929985] (+0.110646118) raw_syscalls:sys_exit: { cpu_id = 1 }, { perf_ip = 0xFFFFFFFF8107B2E8, perf_tid = 19361, perf_pid = 19361, perf_id = 18920, perf_period = 1, common_type = 16, common_flags = 0, common_preempt_count = 1, common_pid = 19361, id = 7, ret = 0 }
> > >
> > > Currently, if we want to find the name and parent of a process, we
> > > have to collect 'sched:sched_switch' event.
> > >
> > > This patch set adds a '--all' option to 'perf convert', converts comm,
> > > fork and exit events to CTF output. CTF user now can track the mapping
> > > by their own.
> > >
> > > v1 -> v2: Report number of sample and non-sample events when finish.
> > > rename opts.non_sample to opts.all.
> > >
> > > Wang Nan (7):
> > > perf ctf: Add value_set_string() helper
> > > perf ctf: Pass convert options through opts structure
> > > perf ctf: Add 'all' option
> > > perf ctf: Prepare collect non-sample events
> > > perf ctf: Generate comm event to CTF output
> > > perf ctf: Add '--all' option for 'perf data convert'
> > > perf ctf: Generate fork and exit events to CTF output
> >
> > I can't compile unless I can include config.h
>
> Waiting for this fix to proceed, but it seems we don't have this covered
just posted it ;-)
> in 'build-test', right? ;-)
right, but we dont cover babletrace stuff in tests/make
jirka
Powered by blists - more mailing lists