This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug translator/4935] support on-the-fly probe enable/disable syntax


------- Additional Comments From mhiramat at redhat dot com  2007-11-27 23:10 -------
(In reply to comment #5)
> Please note that use of this capability would render the probe un-disableable,
> since kernel $context variables need to be evaluated from a single particular
> kprobe rather than anywhere in the script.
> 

Sure, I agree.
I think when we access only global variables in the condition and those 
variables are not changed in the probe point, the probe will be disabled
automagically from other probes where those global variables are changed.
And This optimization depends on where the global variables are changed.
Procfs probes and timer probe are good places to do that.


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=4935

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]