linux-kernel - [RFC Patch 0/4] Enhance perf-events to profile memory accesses using hw-breakpoints

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Date:	Tue, 27 Oct 2009 02:46:37 +0530
From:	"K.Prasad" <prasad@...ux.vnet.ibm.com>
To:	Ingo Molnar <mingo@...e.hu>,
	Frederic Weisbecker <fweisbec@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Alan Stern <stern@...land.harvard.edu>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [RFC Patch 0/4] Enhance perf-events to profile memory accesses
	using hw-breakpoints

Hi All,
	Please review a set of patches that enhance the
perf-events infrastructure to use hw-breakpoints layer to monitor accesses over
kernel-space addresses/symbols, apart from bringing a few related enhancements
to the hw-breakpoint layer.

These patches are still under development and is based off -tip tree
(commit 77a088cd30a7bd2c700bf57544732fff6971305e) and are known to have a few
issues (listed in patch 3/3).

Patch 1/4: Allow per-cpu kernel-space Hardware Breakpoint requests
(originally posted here http://lkml.org/lkml/2009/8/17/172)
Patch 2/4: Allow breakpoints to be enabled/disabled on the fly (without yielding
them to other contenders).
Patch 3/4: Bugfix HW-BKPT: Fix traceback seen when resuming after suspend-to-ram
Patch 4/4: Enhance perf-events to profile memory accesses over kernel symbols

Comments on the same will be appreciated!

Thanks,
K.Prasad

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