Em Thu, Jun 25, 2015 at 06:01:25PM +0200, Jiri Olsa escreveu:
> On Thu, Jun 25, 2015 at 11:39:27AM -0300, Arnaldo Carvalho de Melo wrote:
> > But nah, I'll probably merge what you did and later, if I find the time,
> > do it myself, better to have that new feature than to be picky, right?
>
> righ
On Thu, Jun 25, 2015 at 11:39:27AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jun 23, 2015 at 11:56:18PM +0200, Jiri Olsa escreveu:
> > On Tue, Jun 23, 2015 at 06:01:58PM -0300, Arnaldo Carvalho de Melo wrote:
> > > Em Tue, Jun 23, 2015 at 12:36:03AM +0200, Jiri Olsa escreveu:
> > > > Adding
Em Tue, Jun 23, 2015 at 11:56:18PM +0200, Jiri Olsa escreveu:
> On Tue, Jun 23, 2015 at 06:01:58PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Tue, Jun 23, 2015 at 12:36:03AM +0200, Jiri Olsa escreveu:
> > > Adding support to hold comm name together with pids in
> > > 'struct thread_map'. It will
On Tue, Jun 23, 2015 at 06:01:58PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Tue, Jun 23, 2015 at 12:36:03AM +0200, Jiri Olsa escreveu:
> > Adding support to hold comm name together with pids in
> > 'struct thread_map'. It will be useful for --per-thread
> > option to display task pid together wi
Em Tue, Jun 23, 2015 at 12:36:03AM +0200, Jiri Olsa escreveu:
> Adding support to hold comm name together with pids in
> 'struct thread_map'. It will be useful for --per-thread
> option to display task pid together with task name.
>
> Getting the task name from /proc/$pid/comm.
Do we really need
5 matches
Mail list logo