From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: John Garry <john.garry@huawei.com>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
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, James Clark <James.Clark@arm.com>
Subject: Re: [PATCH 0/4] HiSilicon hip08 uncore PMU events additions
Date: Fri, 4 Oct 2019 12:18:53 -0300 [thread overview]
Message-ID: <20191004151853.GC17687@kernel.org> (raw)
In-Reply-To: <969729ce-6246-6fa7-45c9-3dd9cb07059d@huawei.com>
Em Fri, Oct 04, 2019 at 03:59:44PM +0100, John Garry escreveu:
> On 04/10/2019 15:38, Arnaldo Carvalho de Melo wrote:
> > Em Fri, Oct 04, 2019 at 11:36:58AM -0300, Arnaldo Carvalho de Melo escreveu:
> > > 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.
> > > > 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.
> > It would be really good if somehow we managed to have someone from the
> > ARM community to check and provide a Reviewed-by for those, i.e. someone
> > else than the poster to look at it and check that its ok, would that be
> > possible?
> For this specific case, I'm not sure how much traction or value there would
> be since we're just adding some missing events for custom IP.
Someone else inside your organization? If nobody is available, then so
be it, let that be clear in the JSON file (see below) and then I
wouldn't be waiting for acks/reviewed-by messages for such cases.
> But I do agree that more review of JSONs from the community is required - as
> I brought up here regarding a recent addition:
> https://lore.kernel.org/lkml/749a0b8e-2bfd-28f6-b34d-dc72ef3d3a74@huawei.com/
>
> Can we enforce that at least linux-arm-kernel@lists.infradead.org and/or
> get_maintainer.pl results is cc'ed on anything ARM specific as a start?
I think this should be the case, would you be willing to add a note to
that effect at the top of the JSON files?
And an extra note at tools/perf/pmu-events/README telling users to look
at the json files to figure out what Reviewed-by tags are required for
something to get merged? One extra Reviewed-by would be ok? Who would be
the reviewers for each arch? Would that be at the top of the JSON file?
- Arnaldo
next prev parent reply other threads:[~2019-10-04 15:19 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
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 [this message]
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=20191004151853.GC17687@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=James.Clark@arm.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 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.