Messages in this thread | | | Date | Mon, 2 Jul 2007 14:24:44 +0530 | From | "Abhishek Sagar" <> | Subject | Re: instrumentation and kprobes really still "EXPERIMENTAL"? |
| |
On 7/1/07, Robert P. J. Day <rpjday@mindspring.com> wrote: > isn't kprobes mature enough to not be considered experimental anymore?
That would vary from arch to arch.
> in addition, while most of the KPROBES config options depend on > > KALLSYMS && EXPERIMENTAL && MODULES > > the s390 architecture depends only on > > EXPERIMENTAL && MODULES > > and its instrumentation support is *not* listed as experimental. > > also, the avr32 entry is in the file Kconfig.debug, and depends only > on DEBUG_KERNEL. just an observation.
This probably stems from the episodic growth kprobes across different archs. It can be cleaned up I suppose.
-- Abhishek Sagar
P.S: Adding systemtap in CC. - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |