[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190405123618.GA10844@krava>
Date: Fri, 5 Apr 2019 14:36:18 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Robin Murphy <robin.murphy@....com>
Cc: Florian Fainelli <f.fainelli@...il.com>,
linux-arm-kernel@...ts.infradead.org,
Mark Rutland <mark.rutland@....com>,
Peter Zijlstra <peterz@...radead.org>,
Catalin Marinas <catalin.marinas@....com>,
Will Deacon <will.deacon@....com>,
"open list:PERFORMANCE EVENTS SUBSYSTEM"
<linux-kernel@...r.kernel.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Ingo Molnar <mingo@...hat.com>,
Namhyung Kim <namhyung@...nel.org>
Subject: Re: [PATCH 0/2] arm64: perf: Expose Cortex-A53 micro architectural
events
On Fri, Apr 05, 2019 at 10:36:20AM +0100, Robin Murphy wrote:
> Hi Florian,
>
> On 05/04/2019 00:25, Florian Fainelli wrote:
> > Hi all,
> >
> > This patch series adds support for the Cortex-A53 micro architectural
> > events that I recently had to use for some debugging exercise.
> >
> > Events from 0xC0 - 0xD2 are exposed, others could easily be added later
> > if we wanted to.
>
> As far as I'm aware (which admittedly is not all-the-way far) these events
> should already be understood by userspace, per
> tools/perf/pmu-events/arch/arm64/arm/cortex-a53/* - is there a specific
> reason to need in-kernel definitions?
right, we store events in perf tools in json files, please
check commits changelogs under tools/perf/pmu-events/arch
jirka
Powered by blists - more mailing lists