On Mon, Jun 08, 2015 at 11:03:40AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Jun 04, 2015 at 03:50:55PM +0200, Jiri Olsa escreveu:
> > On Wed, Jun 03, 2015 at 04:25:51PM +0200, Jiri Olsa wrote:
> > > We need fast way to identify evsel as transaction event
> > > for shadow counters
On Mon, Jun 08, 2015 at 11:03:40AM -0300, Arnaldo Carvalho de Melo wrote:
Em Thu, Jun 04, 2015 at 03:50:55PM +0200, Jiri Olsa escreveu:
On Wed, Jun 03, 2015 at 04:25:51PM +0200, Jiri Olsa wrote:
We need fast way to identify evsel as transaction event
for shadow counters computation.
Em Thu, Jun 04, 2015 at 03:50:55PM +0200, Jiri Olsa escreveu:
> On Wed, Jun 03, 2015 at 04:25:51PM +0200, Jiri Olsa wrote:
> > We need fast way to identify evsel as transaction event
> > for shadow counters computation. Currently we are using
> > possition (in evlist) based way.
> >
> > Adding
Em Thu, Jun 04, 2015 at 03:50:55PM +0200, Jiri Olsa escreveu:
On Wed, Jun 03, 2015 at 04:25:51PM +0200, Jiri Olsa wrote:
We need fast way to identify evsel as transaction event
for shadow counters computation. Currently we are using
possition (in evlist) based way.
Adding 'id' into
On Wed, Jun 03, 2015 at 04:25:51PM +0200, Jiri Olsa wrote:
> We need fast way to identify evsel as transaction event
> for shadow counters computation. Currently we are using
> possition (in evlist) based way.
>
> Adding 'id' into 'struct perf_stat' so it can carry transaction
> event ID and we
On Wed, Jun 03, 2015 at 04:25:51PM +0200, Jiri Olsa wrote:
We need fast way to identify evsel as transaction event
for shadow counters computation. Currently we are using
possition (in evlist) based way.
Adding 'id' into 'struct perf_stat' so it can carry transaction
event ID and we can use
6 matches
Mail list logo