This is the mail archive of the systemtap@sources.redhat.com mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Attempting to try out "asynchronous probes" and the current runtime...

From: William Cohen <wcohen at redhat dot com>
To: "Spirakis, Charles" <charles dot spirakis at intel dot com>
Cc: systemtap at sources dot redhat dot com
Date: Mon, 11 Jul 2005 11:27:35 -0400
Subject: Re: Attempting to try out "asynchronous probes" and the current runtime...
References: <2CB9B46A0690824693581340E23B4E10047D2B5A@scsmsx401.amr.corp.intel.com>

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.

This is running on a Pentium M laptop with the mm2 kernel,
CONFIG_PREEMPT_NONE=y, other preemption configs are not set.

-- charles

You might take a look at the fall back timer interrupt mechanism in OProfile to see how it works. In particular look at the linux/driver/oprofile/timer_int.c.

I noticed there are a couple things that were i386 specific in the example, use of regs->eip and task_pt_regs.

-Will

References:
- Attempting to try out "asynchronous probes" and the current runtime...
  - From: Spirakis, Charles

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]