This is the mail archive of the
systemtap@sources.redhat.com
mailing list for the systemtap project.
Re: [RFC] Design + prototype: Multiple handler sets per probe address
- From: Prasanna S Panchamukhi <prasanna at in dot ibm dot com>
- To: "Frank Ch. Eigler" <fche at redhat dot com>
- Cc: systemtap at sources dot redhat dot com
- Date: Mon, 4 Apr 2005 20:12:13 +0530
- Subject: Re: [RFC] Design + prototype: Multiple handler sets per probe address
- References: <20050404123541.GJ1715@in.ibm.com> <20050404133758.GA17776@redhat.com>
- Reply-to: prasanna at in dot ibm dot com
Hi,
On Mon, Apr 04, 2005 at 09:37:58AM -0400, Frank Ch. Eigler wrote:
> Hi -
>
> On Mon, Apr 04, 2005 at 06:05:41PM +0530, Prasanna S Panchamukhi wrote:
> > [...]
> > Another alternative approach to your design would be to define multiple
> > handler sets per probe manager external to kprobes as a kernel module.
> > ..well the external module so called "systemtap" will register only one
> > probe at a given address. [...]
>
> In other words, leave the problem to a higher layer.
>
> This does not look good to me. For example, this would require the
> higher level layer's implementation to be a new separate kernel module
> dedicated to the task. Sharing multiple registration data between
> sibling systemtap sessions (modules), each of which may conclude and
> disappear at any time, is not straightforward.
Its not only about having just separate module, but you can provide a separate
layer/interface on top of existing kprobes interface without even
modifying the existing kprobes interface.
Thanks
Prasanna
--
Prasanna S Panchamukhi
Linux Technology Center
India Software Labs, IBM Bangalore
Ph: 91-80-25044636
<prasanna@in.ibm.com>