From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25399 invoked by alias); 27 Nov 2007 23:10:48 -0000 Received: (qmail 25362 invoked by uid 48); 27 Nov 2007 23:10:37 -0000 Date: Tue, 27 Nov 2007 23:10:00 -0000 Message-ID: <20071127231037.25361.qmail@sourceware.org> From: "mhiramat at redhat dot com" To: systemtap@sources.redhat.com In-Reply-To: <20070817183537.4935.fche@redhat.com> References: <20070817183537.4935.fche@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug translator/4935] support on-the-fly probe enable/disable syntax X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2007-q4/txt/msg00400.txt.bz2 ------- 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.