linux-kernel - Re: perf event group siblings not counting in mainline

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:	Tue, 10 Jan 2012 11:09:42 +0000
From:	Will Deacon <will.deacon@....com>
To:	"a.p.zijlstra@...llo.nl" <a.p.zijlstra@...llo.nl>
Cc:	"mingo@...e.hu" <mingo@...e.hu>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	gregkh@...e.de
Subject: Re: perf event group siblings not counting in mainline

On Sat, Dec 24, 2011 at 12:54:15PM +0000, Will Deacon wrote:
> If I try using perf with event groups on a mainline kernel, only the group
> leader counts:
> 
> 
> linaro@...hed-potato:~$ perf stat --no-scale -g -e task-clock -e cpu-clock -e cs -- ls
> hwb  linux
> 
>  Performance counter stats for 'ls':
> 
>          17.545541 task-clock                #    0.634 CPUs utilized
>           0.000000 cpu-clock
>                  0 cs                        #    0.000 M/sec
> 
>        0.027684984 seconds time elapsed
> 
> 
> This is fixed by b79387ef ("perf: Fix enable_on_exec for sibling events")
> in -next (20111222) but I can't see this queued anywhere for 3.2 (I thought
> I might see it in -rc7).
> 
> Is this going in for the final cut, or will groups just be borked until 3.3?

Now that 3.2 is out with this regression, would it be possible to get this
(b79387ef ("perf: Fix enable_on_exec for sibling events")) into -stable please?

Will
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/