This is the mail archive of the systemtap@sourceware.org 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: Tracking vm activity

From: fche at redhat dot com (Frank Ch. Eigler)
To: "Jun Koi" <junkoi2004 at gmail dot com>
Cc: <systemtap at sources dot redhat dot com>
Date: 08 May 2007 10:15:43 -0400
Subject: Re: Tracking vm activity
References: <462D1F8B.4020607@redhat.com> <fdaac4d50705072008u24441366n60573bc3cf474c91@mail.gmail.com>

"Jun Koi" <junkoi2004@gmail.com> writes:

> [...]
> I found this idea interesting. However, what do you think if the
> machine is SMP, or kernel is preemptive capable?
> [...]
> I cannot figure out how to correlate "enter" and "exit" function
> events in SMP or preemptive case.

In systemtap, a .return probe can refer to parameters of the
*corresponding* .call (function entry) event.  The parameters are
saved in an auxiliary lookup table, indexed by thread-id and nesting
level.  SMP or preemption should not cause any problem.

- FChE

Follow-Ups:
- Re: Tracking vm activity
  - From: Jun Koi

References:
- Tracking vm activity
  - From: William Cohen
- Re: Tracking vm activity
  - From: Jun Koi

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