From: William Cohen <wcohen@redhat.com>
To: Ganapatrao Kulkarni <gklkml16@gmail.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: mark.rutland@arm.com,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
John Garry <john.garry@huawei.com>,
Will Deacon <Will.Deacon@arm.com>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Robert Richter <Robert.Richter@cavium.com>,
Ingo Molnar <mingo@redhat.com>,
jnair@caviumnetworks.com,
Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>,
Jiri Olsa <jolsa@redhat.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Date: Wed, 7 Mar 2018 13:31:35 -0500 [thread overview]
Message-ID: <52328144-3a2a-af03-273b-3a2f3bdadda6@redhat.com> (raw)
In-Reply-To: <CAKTKpr4zMcRLykw8xwWJKf2eiuCrf2RuJ7kexGRQNN7_OdJ=uQ@mail.gmail.com>
On 03/07/2018 12:35 PM, Ganapatrao Kulkarni wrote:
> Hi Will Cohen,
>
> On Wed, Mar 7, 2018 at 8:08 PM, Arnaldo Carvalho de Melo
> <acme@kernel.org> wrote:
>> Em Wed, Mar 07, 2018 at 09:32:05AM -0500, William Cohen escreveu:
>>> On 03/07/2018 06:08 AM, Ganapatrao Kulkarni wrote:
>>>> There is MIDR change on ThunderX2 B0, adding an entry to mapfile
>>>> to enable JSON events for B0.
>>>>
>>>> Signed-off-by: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>
>>
>> Ganapatrao, can you please take this in consideration and if agreeing
>> send a v2 patch?
>>
>> With that I can add an Acked-by: wcohen, Right?
>>
>> - Arnaldo
>>>> ---
>>>> tools/perf/pmu-events/arch/arm64/mapfile.csv | 1 +
>>>> 1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv b/tools/perf/pmu-events/arch/arm64/mapfile.csv
>>>> index e61c9ca..93c5d14 100644
>>>> --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv
>>>> +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv
>>>> @@ -13,4 +13,5 @@
>>>> #
>>>> #Family-model,Version,Filename,EventType
>>>> 0x00000000420f5160,v1,cavium,core
>>>> +0x00000000430f0af0,v1,cavium,core
>>>> 0x00000000410fd03[[:xdigit:]],v1,cortex-a53,core
>>>>
>>>
>>> Hi,
>>> Like the cortex-a53 the last digit '0' of the match for the MIDR should be replaced with [[:xdigit:]] to allow for possible future revisions of chip:
>
> for arm64 implementation, bits 3:0(Revision) and bits 23:20(Variant)
> are ignored/dont-care.
Thanks for pointing that out. See the code masking out those bits in linux/toos/perf/arch/util/header.c. For the ppc64 it just copies the equivalent of the MIDR including the revision bits. Thus, the need for regular expression matching to avoid having to create a new entry for each revision.
-Will
>
>>>
>>> 0x00000000430f0af[[:xdigit:]],v1,cavium,core
>>>
>>>
>>> -Will Cohen
>>
>
> thanks
> Ganapat
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-03-07 18:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 11:08 Ganapatrao Kulkarni
2018-03-07 14:32 ` William Cohen
2018-03-07 14:38 ` Arnaldo Carvalho de Melo
2018-03-07 15:25 ` John Garry
2018-03-07 15:36 ` William Cohen
2018-03-07 17:35 ` Ganapatrao Kulkarni
2018-03-07 18:31 ` William Cohen [this message]
2018-03-08 4:14 ` Ganapatrao Kulkarni
2018-03-09 14:27 ` Ganapatrao Kulkarni
2018-03-09 14:34 ` Arnaldo Carvalho de Melo
2018-03-09 15:58 ` Will Deacon
2018-03-09 17:28 ` Arnaldo Carvalho de Melo
2018-03-09 17:33 ` Arnaldo Carvalho de Melo
2018-03-09 17:45 ` Ganapatrao Kulkarni
2018-03-09 18:00 ` Arnaldo Carvalho de Melo
2018-03-09 18:02 ` Arnaldo Carvalho de Melo
2018-03-09 18:07 ` Ganapatrao Kulkarni
2018-03-15 15:53 ` William Cohen
2018-03-15 16:47 ` John Garry
2018-03-21 2:37 ` William Cohen
2018-03-21 10:58 ` John Garry
2018-03-20 6:27 ` [tip:perf/core] " tip-bot for Ganapatrao Kulkarni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52328144-3a2a-af03-273b-3a2f3bdadda6@redhat.com \
--to=wcohen@redhat.com \
--cc=Robert.Richter@cavium.com \
--cc=Will.Deacon@arm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=ganapatrao.kulkarni@cavium.com \
--cc=gklkml16@gmail.com \
--cc=jnair@caviumnetworks.com \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®