linux-kernel - Re: Perf framework : Cluster based counter support

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] [day] [month] [year] [list]

Date:   Mon, 1 Jul 2019 17:37:13 +0100
From:   Mark Rutland <mark.rutland@....com>
To:     Mukesh Ojha <mojha@...eaurora.org>
Cc:     lkml <linux-kernel@...r.kernel.org>
Subject: Re: Perf framework : Cluster based counter support

On Mon, Jul 01, 2019 at 09:09:33PM +0530, Mukesh Ojha wrote:
> 
> On 6/28/2019 10:29 PM, Mark Rutland wrote:
> > On Fri, Jun 28, 2019 at 10:23:10PM +0530, Mukesh Ojha wrote:
> > > Hi All,
> > Hi Mukesh,
> > 
> > > Is it looks considerable to add cluster based event support to add in
> > > current perf event framework and later in userspace perf to support
> > > such events ?
> > Could you elaborate on what you mean by "cluster based event"?
> > 
> > I assume you mean something like events for a cluster-affine shared
> > resource like some level of cache?
> > 
> > If so, there's a standard pattern for supporting such system/uncore
> > PMUs, see drivers/perf/qcom_l2_pmu.c and friends for examples.
> 
> Thanks Mark for pointing it out.
> Also What is stopping us in adding cluster based event e.g L2 cache hit/miss
> or some other type raw events  in core framework ?

That depends on how the event is exposed.

If it's exposed via the architectural PMU, then it's already accessible
as a raw (cpu-affine) event, regardless of whether that makes sense.

If it's a separate PMU (as I suspect is the case), then it simply has to
be a separate PMU driver.

Thanks,
Mark.