From: "mhiramat at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/4935] support on-the-fly probe enable/disable syntax
Date: Tue, 27 Nov 2007 23:10:00 -0000 [thread overview]
Message-ID: <20071127231037.25361.qmail@sourceware.org> (raw)
In-Reply-To: <20070817183537.4935.fche@redhat.com>
------- 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.
next prev parent reply other threads:[~2007-11-27 23:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 21:37 [Bug translator/4935] New: " fche at redhat dot com
2007-08-24 1:46 ` [Bug translator/4935] " fche at redhat dot com
2007-10-08 16:49 ` mhiramat at redhat dot com
2007-10-08 17:10 ` fche at redhat dot com
2007-11-16 23:40 ` mhiramat at redhat dot com
2007-11-20 16:34 ` Frank Ch. Eigler
2007-11-20 18:57 ` Masami Hiramatsu
2007-11-27 16:02 ` mhiramat at redhat dot com
2007-11-27 16:15 ` fche at redhat dot com
2007-11-27 23:10 ` mhiramat at redhat dot com [this message]
2007-12-04 20:46 ` mhiramat at redhat dot com
2007-12-04 20:47 ` mhiramat at redhat dot com
2007-12-05 17:09 ` fche at redhat dot com
2007-12-05 19:21 ` mhiramat at redhat dot com
2008-01-14 17:13 ` fche at redhat dot com
2008-10-01 21:23 ` mhiramat at redhat dot com
2009-11-20 22:42 ` fche at redhat dot com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071127231037.25361.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).