From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Peter Zijlstra <peterz@infradead.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
bcm-kernel-feedback-list@broadcom.com,
Namhyung Kim <namhyung@kernel.org>, Jiri Olsa <jolsa@redhat.com>,
"moderated list:ARM PMU PROFILING AND DEBUGGING"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] perf vendor events arm64: Map Brahma-B53 CPUID to cortex-a53 events
Date: Thu, 2 May 2019 19:57:25 -0400 [thread overview]
Message-ID: <20190502235725.GB22982@kernel.org> (raw)
In-Reply-To: <46ac3066-fa55-9fb8-dd54-32fb702030cb@gmail.com>
Em Thu, May 02, 2019 at 02:28:02PM -0700, Florian Fainelli escreveu:
> On 4/8/19 9:26 AM, Will Deacon wrote:
> > On Fri, Apr 05, 2019 at 09:50:47AM -0700, Florian Fainelli wrote:
> >> Broadcom's Brahma-B53 CPUs support the same type of events that the
> >> Cortex-A53 supports, recognize its CPUID and map it to the cortex-a53
> >> events.
> >>
> >> Signed-off-by: Florian Fainelli <f.fainelli@gmail.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 59cd8604b0bd..e97c12484bc6 100644
> >> --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv
> >> +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv
> >> @@ -13,6 +13,7 @@
> >> #
> >> #Family-model,Version,Filename,EventType
> >> 0x00000000410fd03[[:xdigit:]],v1,arm/cortex-a53,core
> >> +0x00000000420f100[[:xdigit:]],v1,arm/cortex-a53,core
> >> 0x00000000420f5160,v1,cavium/thunderx2,core
> >> 0x00000000430f0af0,v1,cavium/thunderx2,core
> >> 0x00000000480fd010,v1,hisilicon/hip08,core
> >
> > Acked-by: Will Deacon <will.deacon@arm.com>
>
> Thanks! Can this be picked up?
Thanks, applied to perf/core.
- Arnaldo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Will Deacon <will.deacon@arm.com>, Jiri Olsa <jolsa@redhat.com>,
linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Namhyung Kim <namhyung@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
"moderated list:ARM PMU PROFILING AND DEBUGGING"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] perf vendor events arm64: Map Brahma-B53 CPUID to cortex-a53 events
Date: Thu, 2 May 2019 19:57:25 -0400 [thread overview]
Message-ID: <20190502235725.GB22982@kernel.org> (raw)
In-Reply-To: <46ac3066-fa55-9fb8-dd54-32fb702030cb@gmail.com>
Em Thu, May 02, 2019 at 02:28:02PM -0700, Florian Fainelli escreveu:
> On 4/8/19 9:26 AM, Will Deacon wrote:
> > On Fri, Apr 05, 2019 at 09:50:47AM -0700, Florian Fainelli wrote:
> >> Broadcom's Brahma-B53 CPUs support the same type of events that the
> >> Cortex-A53 supports, recognize its CPUID and map it to the cortex-a53
> >> events.
> >>
> >> Signed-off-by: Florian Fainelli <f.fainelli@gmail.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 59cd8604b0bd..e97c12484bc6 100644
> >> --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv
> >> +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv
> >> @@ -13,6 +13,7 @@
> >> #
> >> #Family-model,Version,Filename,EventType
> >> 0x00000000410fd03[[:xdigit:]],v1,arm/cortex-a53,core
> >> +0x00000000420f100[[:xdigit:]],v1,arm/cortex-a53,core
> >> 0x00000000420f5160,v1,cavium/thunderx2,core
> >> 0x00000000430f0af0,v1,cavium/thunderx2,core
> >> 0x00000000480fd010,v1,hisilicon/hip08,core
> >
> > Acked-by: Will Deacon <will.deacon@arm.com>
>
> Thanks! Can this be picked up?
Thanks, applied to perf/core.
- Arnaldo
next prev parent reply other threads:[~2019-05-02 23:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-05 16:50 [PATCH] perf vendor events arm64: Map Brahma-B53 CPUID to cortex-a53 events Florian Fainelli
2019-04-05 16:50 ` Florian Fainelli
2019-04-08 16:26 ` Will Deacon
2019-04-08 16:26 ` Will Deacon
2019-05-02 21:28 ` Florian Fainelli
2019-05-02 21:28 ` Florian Fainelli
2019-05-02 23:57 ` Arnaldo Carvalho de Melo [this message]
2019-05-02 23:57 ` Arnaldo Carvalho de Melo
2019-05-13 18:04 ` Florian Fainelli
2019-05-13 18:04 ` Florian Fainelli
2019-05-13 19:22 ` Arnaldo Carvalho de Melo
2019-05-13 19:22 ` Arnaldo Carvalho de Melo
2019-05-13 19:30 ` Florian Fainelli
2019-05-13 19:30 ` Florian Fainelli
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=20190502235725.GB22982@kernel.org \
--to=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=f.fainelli@gmail.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=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=will.deacon@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.