[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53110DAB.2010908@redhat.com>
Date: Fri, 28 Feb 2014 17:28:59 -0500
From: Joe Mario <jmario@...hat.com>
To: Davidlohr Bueso <davidlohr@...com>
CC: Don Zickus <dzickus@...hat.com>, Andi Kleen <andi@...stfloor.org>,
acme@...stprotocols.net, LKML <linux-kernel@...r.kernel.org>,
jolsa@...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
Apologies for the resend. My first msg contained html in it.
On 02/28/2014 04:03 PM, 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
David:
It looks like you're running on an older Intel processor, which is missing necessary events for C2C to work.
As Don noted in his patch 00/19, this was primarily developed and tested on Intel's Ivy Bridge platform.
If you rerun this on an Ivy Bridge, it should work fine.
We should add a runtime check for supported platforms.
Joe
> Thanks!
>
>
>
--
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