Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753949AbZGTVWE (ORCPT ); Mon, 20 Jul 2009 17:22:04 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752738AbZGTVWD (ORCPT ); Mon, 20 Jul 2009 17:22:03 -0400 Received: from mail-fx0-f218.google.com ([209.85.220.218]:53233 "EHLO mail-fx0-f218.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751063AbZGTVWC (ORCPT ); Mon, 20 Jul 2009 17:22:02 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=q0MatHz1Xlf0jOcoz4/1/7GShRHW4htCnAFF3E3f8iQGSObRfeyyJC2g4gX3OlG986 xb9hDSe6ahsFl8HIVtvjhqJRZmXWui+rpRe2q7CoQcxmo49RY08I27zeu9fKdhfFv6xx KKYqZ4PNeW8Kp+Hh/b+l/8WuKJzmqKTopgzvU= MIME-Version: 1.0 In-Reply-To: <1248111537.15751.9341.camel@twins> References: <1248109687-7808-1-git-send-email-fweisbec@gmail.com> <1248109687-7808-6-git-send-email-fweisbec@gmail.com> <1248111537.15751.9341.camel@twins> Date: Mon, 20 Jul 2009 17:22:00 -0400 Message-ID: Subject: Re: [RFC][PATCH 5/5] perfcounter: Add support for kernel hardware breakpoints From: =?ISO-8859-1?Q?Fr=E9d=E9ric_Weisbecker?= To: Peter Zijlstra , Masami Hiramatsu Cc: Ingo Molnar , LKML , Steven Rostedt , Thomas Gleixner , Mike Galbraith , Paul Mackerras , Arnaldo Carvalho de Melo , Lai Jiangshan , Anton Blanchard , Li Zefan , Zhaolei , KOSAKI Motohiro , Mathieu Desnoyers , "K . Prasad" , Alan Stern Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1281 Lines: 29 2009/7/20, Peter Zijlstra : > On Mon, 2009-07-20 at 13:08 -0400, Frederic Weisbecker wrote: >> This adds the support for kernel hardware breakpoints in perfcounter. >> It is added as a new type of software counter and can be defined by >> using the counter number 5 and by passsing the address of the >> breakpoint to set through the config attribute. > > This seems to be IP based breakpoints. Are there plans for data based > breakpoints as well? In that case we might want to think about the > namespace issue, we cannot both call them breakpoint/bp etc.. ;-) Nop, by default these breakpoints trigger on READ/WRITE accesses, it's meant for data. The example in the changelog profiles the bkl accesses, not by tracing lock_kernel() or so...but by tracing the kernel_flag spinlock itself. So it's the opposite, we may start thinking about naming issues against possible future plans for IP breakpoint :-) But actually for the latter case, I would suggest Kprobe... Damn, I forgot Masami in the Cc list... -- 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/