mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: William Cohen <wcohen@redhat.com>
To: Ganapatrao Kulkarni <ganapatrao.kulkarni@cavium.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Cc: acme@kernel.org, alexander.shishkin@linux.intel.com,
	jolsa@redhat.com, peterz@infradead.org, mingo@redhat.com,
	john.garry@huawei.com, Will.Deacon@arm.com, mark.rutland@arm.com,
	jnair@caviumnetworks.com, Robert.Richter@cavium.com
Subject: Re: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Date: Wed, 7 Mar 2018 09:32:05 -0500	[thread overview]
Message-ID: <3384d33f-c927-740a-97f1-b20775ef2c7b@redhat.com> (raw)
In-Reply-To: <20180307110803.32418-1-ganapatrao.kulkarni@cavium.com>

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>
> ---
>  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:

0x00000000430f0af[[:xdigit:]],v1,cavium,core


-Will Cohen

  reply	other threads:[~2018-03-07 14:32 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 [this message]
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
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=3384d33f-c927-740a-97f1-b20775ef2c7b@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=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®