Bug 3859 - SystemTap Control Library
Summary: SystemTap Control Library
Status: RESOLVED FIXED
Alias: None
Product: systemtap
Classification: Unclassified
Component: runtime (show other bugs)
Version: unspecified
: P2 enhancement
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on: 1154 4935
Blocks:
  Show dependency tree / graph
 
Reported: 2007-01-11 11:44 UTC by Masami Hiramatsu
Modified: 2010-02-26 01:54 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Masami Hiramatsu 2007-01-11 11:44:12 UTC 
On the view of Middleware, I think SystemTap should be better to 
provide the interfaces for controlling its behavior. For example,
start/stop/pause tracing, read information, record a special
event and so on.

Thanks,
Comment 1 Frank Ch. Eigler 2007-08-21 19:10:16 UTC 
Can you think of something that cannot be accomplished by a cleverly
written script using the future facilities from bug #1154 (procfs interaction),
bug #4935 (on-the-fly probe enable/disable)?
Comment 2 Masami Hiramatsu 2007-08-23 20:55:48 UTC 
(In reply to comment #1)
> Can you think of something that cannot be accomplished by a cleverly
> written script using the future facilities from bug #1154 (procfs interaction),
> bug #4935 (on-the-fly probe enable/disable)?

Sure, it seems good idea. I think users can easily cooperate their applications
and scripts if we implement those facilities (especially, procfs interaction).
(I had just thought that systemtap needed a kind of the interface for
cooperating with various user application.)
Comment 3 Frank Ch. Eigler 2007-08-23 22:15:56 UTC 
OK, let's suspend this bug, and when the other two are done, we'll close this too.
Comment 4 Frank Ch. Eigler 2010-02-26 01:54:41 UTC 
this can be assembled from procfs and to a lesser extent conditional
probes (see bug #10995).