[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20161024094231.GA23322@krava>
Date: Mon, 24 Oct 2016 11:42:31 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: Arnaldo Carvalho de Melo <acme@...nel.org>,
linux-kernel@...r.kernel.org, Linux Weekly News <lwn@....net>,
Andi Kleen <andi@...stfloor.org>,
David Ahern <dsahern@...il.com>,
Don Zickus <dzickus@...hat.com>, Jiri Olsa <jolsa@...nel.org>,
Joe Mario <jmario@...hat.com>,
Namhyung Kim <namhyung@...nel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: [GIT PULL 00/52] New Tool: perf c2c
On Mon, Oct 24, 2016 at 11:23:28AM +0200, Ingo Molnar wrote:
>
> * Jiri Olsa <jolsa@...hat.com> wrote:
>
> > > If I do 'perf report' I get two events:
> > >
> > > Available samples
> > > 24K cpu/mem-loads,ldlat=30/P
> > > 45K cpu/mem-stores/P
> > >
> > > and both have some real data.
> > >
> > > What am I missing?
> >
> > hm, most likely you did not generate any remote HITMs.. if it was on the laptop?
>
> Yeah.
>
> > you might get some results for local HITMs with -d option:
> >
> > $ perf c2c report -d lcl
> >
> > the default display/filter is for Remote HITMs.. perhaps we could be
> > smart enough and switch to local when we found no data for remote
>
> Yeah, this did the trick.
>
> Could we please make sure there's always actionable output by the tool? I.e. it
> should either clearly refuse to work (due to lack of hw), or it should produce
> something meaningful.
ok, will do
thanks,
jirka
Powered by blists - more mailing lists