linux-kernel - Re: [PATCH 0/4] HiSilicon hip08 uncore PMU events additions

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 4 Oct 2019 12:18:53 -0300
From:   Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>
To:     John Garry <john.garry@...wei.com>
Cc:     Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>,
        peterz@...radead.org, mingo@...hat.com,
        alexander.shishkin@...ux.intel.com, jolsa@...hat.com,
        namhyung@...nel.org, linux-kernel@...r.kernel.org,
        linuxarm@...wei.com, will@...nel.org, mark.rutland@....com,
        zhangshaokun@...ilicon.com, James Clark <James.Clark@....com>
Subject: Re: [PATCH 0/4] HiSilicon hip08 uncore PMU events additions

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@...ts.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