This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug kprobes/4748] Kprobes marked EXPERIMENTAL
- From: "rpjday at mindspring dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 7 Jul 2007 11:38:32 -0000
- Subject: [Bug kprobes/4748] Kprobes marked EXPERIMENTAL
- References: <20070707003221.4748.jkenisto@us.ibm.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From rpjday at mindspring dot com 2007-07-07 11:38 -------
Subject: Re: New: Kprobes marked EXPERIMENTAL
On Fri, 7 Jul 2007, jkenisto at us dot ibm dot com wrote:
> If you run make menuconfig (or a sibling thereof), you'll see that kprobes is
> labeled "EXPERIMENTAL". Kprobes has been in Linus's kernel since 2004, so this
> label is rather cautious. One explanation is that KPROBES is in the
> Instrumentation submenu, which itself depends on EXPERIMENTAL. But does that
> mean we have to explicitly mention it in the 'bool "Kprobes..."' line in
> arch/*/Kconfig?
>
> Here's a related discussion on LKML:
> http://www.uwsg.indiana.edu/hypermail/linux/kernel/0707.0/0069.html
i'm tempted to submit a patch that removes the top-level EXPERIMENTAL
dependency from the Instrumentation menu in all those Kconfig files.
if something is truly experimental, it makes more sense that it be
tagged that way individually on a feature-by-feature basis.
want me to do that as a starting point?
rday
--
http://sourceware.org/bugzilla/show_bug.cgi?id=4748
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.