This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: what does 'probe process(PID_OR_NAME).clone' mean?
- From: Ananth N Mavinakayanahalli <ananth at in dot ibm dot com>
- To: David Smith <dsmith at redhat dot com>
- Cc: Systemtap List <systemtap at sources dot redhat dot com>
- Date: Thu, 29 May 2008 17:47:16 +0530
- Subject: Re: what does 'probe process(PID_OR_NAME).clone' mean?
- References: <483D9456.4070107@redhat.com> <483D9542.1040007@redhat.com>
- Reply-to: ananth at in dot ibm dot com
On Wed, May 28, 2008 at 12:24:18PM -0500, David Smith wrote:
Roland,
> For building up to the user's natural perspective on things, I like an
> organization of a few building blocks. First, let me describe the idea
> of a "tracing group". (For now, I'll just talk about it as a semantic
> abstraction and not get into how something would implement it per se.)
> By this I just mean a set of tasks (i.e. threads, in one or more
> processes) that you want to treat uniformally, at least in utrace
> terms. That is, "tracing group" is the coarsest determinant of how you
> treat a thread having an event of potential interest. In utrace terms,
> all threads in the group have the same event mask, the same ops vector,
> and possibly the same engine->data pointer.
Isn't the above same as what you characterize as "sharing" utrace
engines in the utrace TODO?
Something like an aggregate utrace engine will be valuable for uprobes
too.
Ananth