linux-kernel - Re: [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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20091102150503.GE23776@elte.hu>
Date:	Mon, 2 Nov 2009 16:05:04 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	"K.Prasad" <prasad@...ux.vnet.ibm.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Alan Stern <stern@...land.harvard.edu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Paul Mackerras <paulus@...ba.org>
Subject: Re: [RFC Patch 0/4] Enhance perf-events to profile memory accesses
	using hw-breakpoints - ver II


* Frederic Weisbecker <fweisbec@...il.com> wrote:

> Well this ascii art should be a bit more complicated actually. But 
> anyway. Prasad's patchset is another branch of evolution of 
> tracing/hw-breakpoints.
>
> I've expressed my opinion about that in a mail yesterday. I basically 
> think it limits the perf events possibilities and rewrites the context 
> binding / register allocation that perf already handles.

Ok, in hindsight i agree with your point of view - we really dont want a 
duplicate layer but a single handler/arbitrer of hw-breakpoint state.

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