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 memory map changes

From: fche at redhat dot com (Frank Ch. Eigler)
To: David Smith <dsmith at redhat dot com>
Cc: Jim Keniston <jkenisto at us dot ibm dot com>, Systemtap List <systemtap at sources dot redhat dot com>
Date: Fri, 30 May 2008 18:34:11 -0400
Subject: Re: tracking memory map changes
References: <48402E5F.2080301@redhat.com> <1212169085.4010.33.camel@dyn9047018139.beaverton.ibm.com> <48404581.1000300@redhat.com>

David Smith <dsmith@redhat.com> writes:

> [...]
>> It'd also be good to watch for vm areas going away.  [...]

Absolutely.  We must do that.

> If CONFIG_PROFILING is on, sys_munmap() has a hook built into it
> that we might be able to use.  [...]  If that won't work, we'll have
> to fall back to something similar to what we decide to do for mmap
> tracing.

Considering that we'll already intercept mmap, we might as well
intercept munmap for the same processes using the same mechanism.

- FChE

References:
- tracking memory map changes
  - From: David Smith
- Re: tracking memory map changes
  - From: Jim Keniston
- Re: tracking memory map changes
  - From: David Smith

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