linux-kernel - RE: [PATCH] drivers/perf: hisi: Add identifier sysfs file

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]

Message-ID: <DB8PR04MB67958EC5610A5AE4E7B0AB1AE62E0@DB8PR04MB6795.eurprd04.prod.outlook.com>
Date:   Tue, 1 Sep 2020 10:18:14 +0000
From:   Joakim Zhang <qiangqing.zhang@....com>
To:     John Garry <john.garry@...wei.com>, Will Deacon <will@...nel.org>
CC:     "zhangshaokun@...ilicon.com" <zhangshaokun@...ilicon.com>,
        "mark.rutland@....com" <mark.rutland@....com>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "jolsa@...hat.com" <jolsa@...hat.com>,
        "linuxarm@...wei.com" <linuxarm@...wei.com>
Subject: RE: [PATCH] drivers/perf: hisi: Add identifier sysfs file


> -----Original Message-----
> From: John Garry <john.garry@...wei.com>
> Sent: 2020年7月15日 16:23
> To: Will Deacon <will@...nel.org>
> Cc: zhangshaokun@...ilicon.com; mark.rutland@....com;
> linux-arm-kernel@...ts.infradead.org; linux-kernel@...r.kernel.org; Joakim
> Zhang <qiangqing.zhang@....com>; jolsa@...hat.com;
> linuxarm@...wei.com
> Subject: Re: [PATCH] drivers/perf: hisi: Add identifier sysfs file
> 
> Hi Will,
> 
> >
> > On Wed, Jun 17, 2020 at 09:05:11PM +0800, John Garry wrote:
> >> To allow userspace to identify the specific implementation of the
> >> device, add an "identifier" sysfs file.
> >>
> >> Encoding is as follows:
> >> hi1620: 0x0	(aka hip08)
> >> hi1630: 0x30
> >>
> >> Signed-off-by: John Garry <john.garry@...wei.com>
> >
> > I'm struggling a bit to track this. If you still think it's worth
> > pursuing, please could you post a series with a cover-letter
> > describing what this is for, a link to the userspace changes and then
> > patches for all the PMU drivers that need updating?
> 
> There is no hi1630 userspace support yet.
> 
> So what I can do is post updated userspace support (including hi1630), and then
> post kernel parts together for all drivers we could initially support.
> 
> @Joakim, I'll pick your imx driver changes here, if you don't mind.

Hi John,

Any update about adding system pmu support in perf tool? Will you continue upstreaming it? Feel free let me know if you need I do the test.

Best Regards,
Joakim Zhang