linux-kernel - Oprofile Regression Caused by commit e5d1367f17ba6a6fed5fd8b74e4d5720923e0c25 on PPC

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

Date:	Fri, 7 Oct 2011 16:42:47 -0400
From:	Eric B Munson <emunson@...bm.net>
To:	eranian@...gle.com
Cc:	a.p.zijlstra@...llo.nl, mingo@...e.hu, anton@...ba.org,
	linux-kernel@...r.kernel.org, paulus@...ba.org, hbabu@...ibm.com
Subject: Oprofile Regression Caused by commit
 e5d1367f17ba6a6fed5fd8b74e4d5720923e0c25 on PPC

This commit seems to have caused a regression with oprofile.  It is fairly easy
to trigger, simply run oprofile monitoring an event that will fire (something
frequent like CPU cycles) causes oprofile to fail saying that the PMU is in use.
If I disable CONFIG_CGROUP_PERF, everything goes back to working.  I suspect the
problem is that the PMU is being initialized without being reserved for perf.  I
am not yet sure of the right fix yet so if you have any suggestions I would
appreciate them.

Eric

Download attachment "signature.asc" of type "application/pgp-signature" (491 bytes)