This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [PATCH v3] Tracepoint Tapset for Memory Subsystem
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Rajasekhar Duddu <rajduddu at linux dot vnet dot ibm dot com>
- Cc: systemtap at sources dot redhat dot com
- Date: Wed, 07 Oct 2009 15:51:07 -0400
- Subject: Re: [PATCH v3] Tracepoint Tapset for Memory Subsystem
- References: <20090919050102.GA3767@rajduddu> <4AB90BE0.4030405@redhat.com> <y0mmy4mishg.fsf@fche.csb> <4AB94A1B.4090801@redhat.com> <20090924180817.GA9698@rajduddu> <4ABD3B2B.4020107@redhat.com> <20090930101156.GA3792@rajduddu> <20091002151344.GA9516@rajduddu> <y0mocokgxe2.fsf@fche.csb> <20091007130728.GA6574@rajduddu>
Rajasekhar Duddu <rajduddu@linux.vnet.ibm.com> writes:
> [...]
>> Nice. I thought that the raison d'etre for these aliases was to
>> abstract the presence or absence of tracepoints, so is there no
>> fallback kprobe available? Something like this:
>>
> Fallback kprobe is not available for other memory functions because
> the variables exported by them are will be modified.
Could you elaborate? Do you mean that the same values may not be
available from a kprobe context?
- FChE