[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7e209e42-362e-7767-2b94-62239c62e70d@huawei.com>
Date: Wed, 6 Dec 2017 08:34:59 +0000
From: John Garry <john.garry@...wei.com>
To: Andi Kleen <ak@...ux.intel.com>
CC: <mark.rutland@....com>, <peterz@...radead.org>,
<catalin.marinas@....com>, <will.deacon@....com>,
<linuxarm@...wei.com>, <acme@...nel.org>,
<linux-kernel@...r.kernel.org>, <zhangshaokun@...ilicon.com>,
<alexander.shishkin@...ux.intel.com>, <mingo@...hat.com>,
<xuwei5@...ilicon.com>, <ganapatrao.kulkarni@...ium.com>,
<namhyung@...nel.org>, <wcohen@...hat.com>, <jolsa@...hat.com>,
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [RFC PATCH 2/5] perf jevents: add support for arch recommended
events
On 05/12/2017 17:27, Andi Kleen wrote:
> On Wed, Dec 06, 2017 at 12:13:16AM +0800, John Garry wrote:
>> For some architectures (like arm64), there are architecture-
>> defined recommended events. Vendors may not be obliged to
>> follow the recommendation and may implement their own pmu
>> event for a specific event cod
>
> I would just duplicate the architected events into the different
> vendor files. Then you wouldn't need all this mess.
>
This is what we were originally doing:
https://patchwork.kernel.org/patch/10010859/
But then we thought that we could avoid duplicating all these events for
every platform from every vendor. Most, if not all, vendors will
implement the events as recommended for any platform, so much
unnecessary duplication.
cheers,
John
> -Andi
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
> .
>
Powered by blists - more mailing lists