From: acme@kernel.org (Arnaldo Carvalho de Melo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0
Date: Fri, 9 Mar 2018 15:00:40 -0300 [thread overview]
Message-ID: <20180309180040.GI8347@kernel.org> (raw)
In-Reply-To: <CAKTKpr7AQQVQKpQyeDObXvgq1Cps7K7STW2TngjFmOjmCRXQWQ@mail.gmail.com>
Em Fri, Mar 09, 2018 at 11:15:16PM +0530, Ganapatrao Kulkarni escreveu:
> Hi Arnaldo,
>
> On Fri, Mar 9, 2018 at 11:03 PM, Arnaldo Carvalho de Melo
> <arnaldo.melo@gmail.com> wrote:
> > Em Fri, Mar 09, 2018 at 03:58:09PM +0000, Will Deacon escreveu:
> >> On Fri, Mar 09, 2018 at 11:34:15AM -0300, Arnaldo Carvalho de Melo wrote:
> >> > Em Fri, Mar 09, 2018 at 07:57:04PM +0530, Ganapatrao Kulkarni escreveu:
> >> > > Hi Arnaldo,
> >> > >
> >> > > can you please pull-in this patch?
> >> >
> >> > So everybody is Ok with this? Can I have some Acked-by: from subject
> >> > matter experts?
> >>
> >> The original patch looks fine to me:
> >>
> >> Acked-by: Will Deacon <will.deacon@arm.com>
> >
> > Ok, so, as John mentioned in another message in his thread, this
> > conflicts with a series he sent and that Ganapatrao acked and I already
> > applied, I looked at it and think this patch should turn into the patch
> > at the end of this message, which I'm applying with the commit log
> > message in the original patch in this thread, Ack?
>
> >
> > - Arnaldo
> >
> > diff --git a/tools/perf/pmu-events/arch/arm64/mapfile.csv b/tools/perf/pmu-events/arch/arm64/mapfile.csv
> > index 8f11aeb003a9..624e8cae6e86 100644
> > --- a/tools/perf/pmu-events/arch/arm64/mapfile.csv
> > +++ b/tools/perf/pmu-events/arch/arm64/mapfile.csv
> > @@ -13,5 +13,5 @@
> > #
> > #Family-model,Version,Filename,EventType
> > 0x00000000410fd03[[:xdigit:]],v1,arm/cortex-a53,core
> > -0x00000000420f5160,v1,cavium/thunderx2,core
> > +0x00000000430f0af0,v1,cavium/thunderx2,core
> > 0x00000000480fd010,v1,hisilicon/hip08,core
>
> please do not delete existing entry, add additional entry.
> > +0x00000000430f0af0,v1,cavium/thunderx2,core
Ok, my bad, I think my eyes are failing me, I swear I saw them in the
original patch, which is not the case...
Ok, will add, together with Will's Acked-by
Thanks,
- Arnaldo
next prev parent reply other threads:[~2018-03-09 18:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-07 11:08 [PATCH] perf vendor events arm64: Enable JSON events for ThunderX2 B0 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
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 [this message]
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
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=20180309180040.GI8347@kernel.org \
--to=acme@kernel.org \
--cc=linux-arm-kernel@lists.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;
as well as URLs for NNTP newsgroup(s).