[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 03 Mar 2014 10:21:45 -0800
From: Davidlohr Bueso <davidlohr@...com>
To: Don Zickus <dzickus@...hat.com>
Cc: Andi Kleen <andi@...stfloor.org>, acme@...stprotocols.net,
LKML <linux-kernel@...r.kernel.org>, jolsa@...hat.com,
jmario@...hat.com, fowles@...each.com, eranian@...gle.com,
Arnaldo Carvalho de Melo <acme@...hat.com>,
David Ahern <dsahern@...il.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Mike Galbraith <efault@....de>,
Paul Mackerras <paulus@...ba.org>,
Peter Zijlstra <peterz@...radead.org>,
Richard Fowles <rfowles@...hat.com>
Subject: Re: [PATCH 08/19] perf c2c: Shared data analyser
On Mon, 2014-03-03 at 10:05 -0500, Don Zickus wrote:
> On Fri, Feb 28, 2014 at 01:03:31PM -0800, Davidlohr Bueso wrote:
> > On Fri, 2014-02-28 at 14:46 -0500, Don Zickus wrote:
> > > On Fri, Feb 28, 2014 at 11:08:59AM -0800, Andi Kleen wrote:
> > > > Don Zickus <dzickus@...hat.com> writes:
> > > > > +
> > > > > +static const struct perf_evsel_str_handler handlers[] = {
> > > > > + { "cpu/mem-loads,ldlat=30/pp", perf_c2c__process_load, },
> > > > > + { "cpu/mem-stores/pp", perf_c2c__process_store, },
> > > >
> >
> > Hmm I'm getting this when running a simple record command.
> >
> > invalid or unsupported event: 'cpu/mem-loads/pp'
> >
> > This only occurs with c2c, other subcommands work normally. It's as if
> > it were an old kernel, but it's Linus' latest. Is this an issue with the
> > patch or something I'm missing?
> >
> > Furthermore, I see:
> > ls /sys/bus/event_source/devices/cpu/events
> > branch-instructions branch-misses cache-misses cache-references cpu-cycles instructions mem-loads
>
> Hmm, so based on Andi's reply, I am assuming you are running on a Westmere
> (or Nehalem) due to the lack of mem-stores.
Indeed, I had definitely overlooked this detail.
Performance Events: PEBS fmt1+, 16-deep LBR, Westmere events, Broken BIOS detected, complain to your hardware vendor.
Thanks,
Davidlohr
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists