linux-kernel - Re: [PATCH v6 06/10] perf metricgroup: Fix metrics using aliases covering multiple PMUs

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:   Mon, 7 Dec 2020 18:02:08 +0000
From:   John Garry <john.garry@...wei.com>
To:     Arnaldo Carvalho de Melo <acme@...nel.org>
CC:     <peterz@...radead.org>, <mingo@...hat.com>, <mark.rutland@....com>,
        <alexander.shishkin@...ux.intel.com>, <jolsa@...hat.com>,
        <namhyung@...nel.org>, <will@...nel.org>,
        <mathieu.poirier@...aro.org>, <leo.yan@...aro.org>,
        <irogers@...gle.com>, <qiangqing.zhang@....com>,
        <kjain@...ux.ibm.com>, <linux-kernel@...r.kernel.org>,
        <zhangshaokun@...ilicon.com>,
        <linux-arm-kernel@...ts.infradead.org>, <linuxarm@...wei.com>,
        <kan.liang@...ux.intel.com>, <kim.phillips@....com>,
        <ak@...ux.intel.com>
Subject: Re: [PATCH v6 06/10] perf metricgroup: Fix metrics using aliases
 covering multiple PMUs

On 07/12/2020 17:19, Arnaldo Carvalho de Melo wrote:
> Next time please try to provides a Fixes: tag to help with
> backporting/stable@...nel.org  work.
> 

Hi Arnaldo,

I know you asked me this before Re. fixes tags ... but I don't know any 
cases of "metrics using aliases covering multiple PMUs" in mainline 
today (which this patch addresses). If there are some, then I guess that 
they are broken and we should seek them out.

Note that this topic was discussed here initially:
https://lore.kernel.org/linux-perf-users/CAP-5=fUy6FOszNRwJF6ZNpqQSSyrnLPV6GbkEcZMqAhUp3X0ZA@mail.gmail.com/

There has been much churn on the metric code recently, so prob not a 
straight stable backport; as such, I would prefer to know some metric 
was broken and verify we fix it.

If you have any better ideas to handle this, then please let me know.

Cheers,
John