This is the mail archive of the
systemtap@sources.redhat.com
mailing list for the systemtap project.
Re: Output Redesign in SystemTap Runtime
- From: Martin Hunt <hunt at redhat dot com>
- To: Roland McGrath <roland at redhat dot com>
- Cc: "systemtap at sources dot redhat dot com" <systemtap at sources dot redhat dot com>
- Date: Mon, 25 Apr 2005 21:09:08 -0700
- Subject: Re: Output Redesign in SystemTap Runtime
- Organization: Red Hat Inc.
- References: <200504260201.j3Q21oF4011249@magilla.sf.frob.com>
On Mon, 2005-04-25 at 19:01 -0700, Roland McGrath wrote:
> > 7. What about probes with custom GUI interfaces? Do we define a way for
> > stpd to fork and forward data to a GUI app, or do we simply structure
> > stpd so anyone can grab the sources and easily build a custom version of
> > it?
>
> What about having stpd just do the set up of an independent channel that
> something else can use? i.e., a new netlink socket, or a new named relayfs
> channel (I'm glossing over the details because I don't remember the details
> of relayfs clearly). If necessary, we could provide a small library for
> applications paired with some probe kernel runtime interfaces for setting
> up and using such channels. It's possible to do something like have an
> application contact stpd and get back a file descriptor for its channel.
That's what I meant by the first option above. I imagine that the
SystemTap script would specify an executable to receive the data and
stpd would start that up and send data to it.
Martin