From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-6628-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 20874 invoked by alias); 7 Jul 2007 00:32:35 -0000
Received: (qmail 19656 invoked by uid 48); 7 Jul 2007 00:32:22 -0000
Date: Sat, 07 Jul 2007 00:32:00 -0000
From: "jkenisto at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Message-ID: <20070707003221.4748.jkenisto@us.ibm.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug kprobes/4748] New: Kprobes marked EXPERIMENTAL
X-Bugzilla-Reason: AssignedTo
Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <systemtap.sourceware.org>
List-Subscribe: <mailto:systemtap-subscribe@sourceware.org>
List-Post: <mailto:systemtap@sourceware.org>
List-Help: <mailto:systemtap-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: systemtap-owner@sourceware.org
X-SW-Source: 2007-q3/txt/msg00034.txt.bz2

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

-- 
           Summary: Kprobes marked EXPERIMENTAL
           Product: systemtap
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: kprobes
        AssignedTo: systemtap at sources dot redhat dot com
        ReportedBy: jkenisto at us dot ibm dot com


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.