linux-kernel - [PATCH 0/6] perf: Use common PMU interrupt disabled code on all architectures

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:	Sun, 15 Jun 2014 01:59:10 -0400 (EDT)
From:	Vince Weaver <vincent.weaver@...ne.edu>
To:	linux-kernel@...r.kernel.org
cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Ingo Molnar <mingo@...hat.com>,
	Vineet Gupta <vgupta@...opsys.com>,
	Steven Miao <realmz6@...il.com>,
	James Hogan <james.hogan@...tec.com>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Paul Mackerras <paulus@...ba.org>,
	Cody P Schafer <cody@...ux.vnet.ibm.com>,
	linux-sh@...r.kernel.org,
	Hendrik Brueckner <brueckner@...ux.vnet.ibm.com>,
	Martin Schwidefsky <schwidefsky@...ibm.com>,
	Heiko Carstens <heiko.carstens@...ibm.com>
Subject: [PATCH 0/6] perf: Use common PMU interrupt disabled code on all
 architectures

Now that "perf/x86: Use common PMU interrupt disabled code"
(c184c980de30dc) was merged, I went and audited all of the
architectures.  The following patchset attempts to move
all of the ones that have code disabling sampled events
due to lack of overflow interrupt to the new common code.

ARM and x86 were already updated with the original changeset.

Note that this is an ABI change in some cases, as many
architectures returned EINVAL previously rather than
EOPNOTSUPP.

Unfortunately these patches are not tested at all, as I don't have
access to the hardware.

--
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/