This is the mail archive of the
systemtap@sources.redhat.com
mailing list for the systemtap project.
Re: Attempting to try out "asynchronous probes" and the currentruntime...
- From: Martin Hunt <hunt at redhat dot com>
- To: "Spirakis, Charles" <charles dot spirakis at intel dot com>
- Cc: "systemtap at sources dot redhat dot com" <systemtap at sources dot redhat dot com>
- Date: Wed, 13 Jul 2005 09:37:07 -0700
- Subject: Re: Attempting to try out "asynchronous probes" and the currentruntime...
- Organization: Red Hat Inc.
- References: <2CB9B46A0690824693581340E23B4E10047D2B5A@scsmsx401.amr.corp.intel.com>
On Wed, 2005-07-06 at 20:31 -0700, Spirakis, Charles wrote:
> All --
>
> I'm playing around with an "asynchronous probe" concept and the
> current
> runtime using simple os timers (code is below). Anyone have experience
> with task_pt_regs() function? As you can see, I'm trying to grab the
> "current" pt_regs in the home of seeing the eip at the time of the
> timer
> interrupt, but the data I get is not what I'd hoped.
I tried to figure out that one for some runtime functions and never
found a solution.
Did you consider using the builtin kernel profiling? oprofile uses it.
It looks like you could take whats in drivers/oprofile and replace all
the data collection and transport stuff with runtime functions and have
a profiler that worked nicely with systemtap.
Martin