Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755420Ab0ANMUc (ORCPT ); Thu, 14 Jan 2010 07:20:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755307Ab0ANMUc (ORCPT ); Thu, 14 Jan 2010 07:20:32 -0500 Received: from bombadil.infradead.org ([18.85.46.34]:45380 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755087Ab0ANMUb (ORCPT ); Thu, 14 Jan 2010 07:20:31 -0500 Subject: Re: [RFC] [PATCH 7/7] Ftrace plugin for Uprobes From: Peter Zijlstra To: Mark Wielaard Cc: Srikar Dronamraju , Ingo Molnar , Arnaldo Carvalho de Melo , Ananth N Mavinakayanahalli , utrace-devel , Jim Keniston , Frederic Weisbecker , Masami Hiramatsu , Maneesh Soni , LKML In-Reply-To: <1263471411.23962.13.camel@springer.wildebeest.org> References: <20100111122521.22050.3654.sendpatchset@srikar.in.ibm.com> <20100111122608.22050.94088.sendpatchset@srikar.in.ibm.com> <1263468191.4244.300.camel@laptop> <1263468575.4244.306.camel@laptop> <1263471411.23962.13.camel@springer.wildebeest.org> Content-Type: text/plain; charset="UTF-8" Date: Thu, 14 Jan 2010 13:19:56 +0100 Message-ID: <1263471596.4244.310.camel@laptop> Mime-Version: 1.0 X-Mailer: Evolution 2.28.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1430 Lines: 32 On Thu, 2010-01-14 at 13:16 +0100, Mark Wielaard wrote: > On Thu, 2010-01-14 at 12:29 +0100, Peter Zijlstra wrote: > > On Thu, 2010-01-14 at 12:23 +0100, Peter Zijlstra wrote: > > > On Mon, 2010-01-11 at 17:56 +0530, Srikar Dronamraju wrote: > > > > This patch implements ftrace plugin for uprobes. > > > > > > Right, like others have said, trace events is a much saner interface. > > > > > > So the easiest way I can see that working is to register uprobes against > > > a file (not a pid). > > > > Just to clarify, this means you can do things like: > > > > p:uprobe_event dso:symbol[+offs] > > > > Irrespective of whether there are any current user of that file. > > Yes, that is a good idea, you can then also refine that with a filter on > a target pid. That is what systemtap also does, you define files > (whether they are executables or shared libraries, etc) plus > symbols/offsets/etc as targets and monitor when they get mapped in > (either system wide, per executable or pid based). Well, the pid part is more the concern of the consumer of the trace-event. The event itself is task invariant and only cares about the particular code in question getting executed. -- 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/