Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755337AbZKBPFY (ORCPT ); Mon, 2 Nov 2009 10:05:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754979AbZKBPFX (ORCPT ); Mon, 2 Nov 2009 10:05:23 -0500 Received: from mx3.mail.elte.hu ([157.181.1.138]:48934 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754764AbZKBPFW (ORCPT ); Mon, 2 Nov 2009 10:05:22 -0500 Date: Mon, 2 Nov 2009 16:05:04 +0100 From: Ingo Molnar To: Frederic Weisbecker Cc: "K.Prasad" , LKML , Steven Rostedt , Alan Stern , Andrew Morton , Paul Mackerras Subject: Re: [RFC Patch 0/4] Enhance perf-events to profile memory accesses using hw-breakpoints - ver II Message-ID: <20091102150503.GE23776@elte.hu> References: <20091028155827.GA8604@in.ibm.com> <20091029081917.GC26970@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-01-05) X-ELTE-SpamScore: 0.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=0.0 required=5.9 tests=none autolearn=no SpamAssassin version=3.2.5 _SUMMARY_ Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 816 Lines: 20 * Frederic Weisbecker 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/