On Thu, Jan 14, 2010 at 01:29:09PM +0100, Peter Zijlstra wrote:
On Thu, 2010-01-14 at 13:23 +0100, Frederic Weisbecker wrote:
I see, so what you suggest is to have the probe set up
as generic first. Then the process that activates it
becomes a consumer, right?
Right, so either we have
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
On Thu, Jan 14, 2010 at 12:23:11PM +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
On Thu, 2010-01-14 at 12:35 +0100, Frederic Weisbecker wrote:
On Thu, Jan 14, 2010 at 12:23:11PM +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
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
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.
On Thu, Jan 14, 2010 at 12:43:01PM +0100, Peter Zijlstra wrote:
On Thu, 2010-01-14 at 12:35 +0100, Frederic Weisbecker wrote:
On Thu, Jan 14, 2010 at 12:23:11PM +0100, Peter Zijlstra wrote:
On Mon, 2010-01-11 at 17:56 +0530, Srikar Dronamraju wrote:
This patch implements ftrace plugin
Steven Rostedt wrote:
On Tue, 2010-01-12 at 05:54 +0100, Frederic Weisbecker wrote:
Now what if I want to launch ls and want to profile a function
inside. What can I do with a trace event. I can't create the
probe event based on a pid as I don't know it in advance.
I could give it the ls
Masami Hiramatsu wrote:
Steven Rostedt wrote:
On Tue, 2010-01-12 at 05:54 +0100, Frederic Weisbecker wrote:
Now what if I want to launch ls and want to profile a function
inside. What can I do with a trace event. I can't create the
probe event based on a pid as I don't know it in advance.
I
Frederic Weisbecker fweis...@gmail.com writes:
[...]
This is much more tricky in the case of uprobes as I see two
ways to work with it:
- probing on an already running process
- probing on a process we are about to run
[...]
As you might expect, in systemtap we've had to figure out this
Hi -
As you might expect, in systemtap we've had to figure out this area
some time ago. We use another utrace consumer called task finder [...]
So, could you tell us how the task-finder works and is implemented?
The code may be found at runtime/task_finder* in the systemtap sources.
On Mon, Jan 11, 2010 at 05:56:08PM +0530, Srikar Dronamraju wrote:
This patch implements ftrace plugin for uprobes.
Description:
Ftrace plugin provides an interface to dump data at a given address, top of
the stack and function arguments when a user program calls a specific
function.
So,
12 matches
Mail list logo
