[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160223153442.GE15284@kernel.org>
Date: Tue, 23 Feb 2016 12:34:42 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Jiri Olsa <jolsa@...nel.org>, lkml <linux-kernel@...r.kernel.org>,
David Ahern <dsahern@...il.com>,
Ingo Molnar <mingo@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Stephane Eranian <eranian@...gle.com>,
Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH 06/23] perf mem: Check for memory events support
Em Tue, Feb 23, 2016 at 04:29:57PM +0100, Jiri Olsa escreveu:
> On Tue, Feb 23, 2016 at 12:18:14PM -0300, Arnaldo Carvalho de Melo wrote:
> > Em Mon, Feb 15, 2016 at 09:34:36AM +0100, Jiri Olsa escreveu:
> > > Check if current kernel support available memory events
> > > and display the status within -e list option:
> > >
> > > $ perf mem record -e list
> > > [ok] ldlat-loads
> > > [ok] ldlat-stores
> > Can't this be:
> > $ perf mem record -e list
> > ldlat-loads: Available on this machine
> > ldlat-stores: Available on this machine
> hum IMO that would be quite long list if DATALA events will
> get in, so I wanted something short and punchy ;-)
> how about plaing it into back as you suggested
> with just 'available'
>
> $ perf mem record -e list
> ldlat-loads: available
> ldlat-stores: available
Fair enough, this is more in line with, say, 'perf test' output, i.e.:
$ perf foo
something: status/result
- Arnaldo
Powered by blists - more mailing lists