From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: John Garry <john.garry@huawei.com>
Cc: peterz@infradead.org, mingo@redhat.com,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
namhyung@kernel.org, linux-kernel@vger.kernel.org,
linuxarm@huawei.com, will@kernel.org, mark.rutland@arm.com,
zhangshaokun@hisilicon.com
Subject: Re: [PATCH 0/4] HiSilicon hip08 uncore PMU events additions
Date: Fri, 4 Oct 2019 11:36:58 -0300 [thread overview]
Message-ID: <20191004143658.GA17687@kernel.org> (raw)
In-Reply-To: <27e693fd-124e-1aa8-3b8a-62301a5a1d10@huawei.com>
Em Fri, Oct 04, 2019 at 03:30:07PM +0100, John Garry escreveu:
> On 04/09/2019 16:54, John Garry wrote:
> > This patchset adds some missing uncore PMU events for the hip08 arm64
> > platform.
> >
> > The missing events were originally mentioned in
> > https://lkml.org/lkml/2019/6/14/645, when upstreaming the JSONs initially.
> >
> > It also includes a fix for a DDRC eventname.
>
> Hi guys,
>
> Could I get these JSON updates picked up please? Maybe they were missed
> earlier. Let me know if I should re-post.
Looking at them now.
- Arnaldo
> Thanks in advance,
> John
>
> >
> > John Garry (4):
> > perf jevents: Fix Hisi hip08 DDRC PMU eventname
> > perf jevents: Add some missing events for Hisi hip08 DDRC PMU
> > perf jevents: Add some missing events for Hisi hip08 L3C PMU
> > perf jevents: Add some missing events for Hisi hip08 HHA PMU
> >
> > .../arm64/hisilicon/hip08/uncore-ddrc.json | 16 +++++-
> > .../arm64/hisilicon/hip08/uncore-hha.json | 23 +++++++-
> > .../arm64/hisilicon/hip08/uncore-l3c.json | 56 +++++++++++++++++++
> > 3 files changed, 93 insertions(+), 2 deletions(-)
> >
>
--
- Arnaldo
next prev parent reply other threads:[~2019-10-04 14:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 15:54 [PATCH 0/4] HiSilicon hip08 uncore PMU events additions John Garry
2019-09-04 15:54 ` [PATCH 1/4] perf jevents: Fix Hisi hip08 DDRC PMU eventname John Garry
2019-10-21 23:19 ` [tip: perf/core] perf vendor events arm64: " tip-bot2 for John Garry
2019-09-04 15:54 ` [PATCH 2/4] perf jevents: Add some missing events for Hisi hip08 DDRC PMU John Garry
2019-10-21 23:19 ` [tip: perf/core] perf vendor events arm64: " tip-bot2 for John Garry
2019-09-04 15:54 ` [PATCH 3/4] perf jevents: Add some missing events for Hisi hip08 L3C PMU John Garry
2019-10-21 23:19 ` [tip: perf/core] perf vendor events arm64: " tip-bot2 for John Garry
2019-09-04 15:54 ` [PATCH 4/4] perf jevents: Add some missing events for Hisi hip08 HHA PMU John Garry
2019-10-21 23:19 ` [tip: perf/core] perf vendor events arm64: " tip-bot2 for John Garry
2019-10-04 14:30 ` [PATCH 0/4] HiSilicon hip08 uncore PMU events additions John Garry
2019-10-04 14:36 ` Arnaldo Carvalho de Melo [this message]
2019-10-04 14:38 ` Arnaldo Carvalho de Melo
2019-10-04 14:59 ` Will Deacon
2019-10-04 14:59 ` John Garry
2019-10-04 15:18 ` Arnaldo Carvalho de Melo
2019-10-04 16:30 ` John Garry
2019-10-04 19:06 ` Arnaldo Carvalho de Melo
2019-10-07 13:40 ` John Garry
2019-10-09 1:14 ` Shaokun Zhang
2019-10-15 15:16 ` Arnaldo Carvalho de Melo
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=20191004143658.GA17687@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=john.garry@huawei.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=will@kernel.org \
--cc=zhangshaokun@hisilicon.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 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).