From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18554 invoked by alias); 9 Jul 2007 04:48:02 -0000 Received: (qmail 18505 invoked by alias); 9 Jul 2007 04:47:51 -0000 Date: Mon, 09 Jul 2007 04:48:00 -0000 Message-ID: <20070709044751.18504.qmail@sourceware.org> From: "ananth at in dot ibm dot com" To: systemtap@sources.redhat.com In-Reply-To: <20070707003221.4748.jkenisto@us.ibm.com> References: <20070707003221.4748.jkenisto@us.ibm.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug kprobes/4748] Kprobes marked EXPERIMENTAL 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-q3/txt/msg00044.txt.bz2 ------- Additional Comments From ananth at in dot ibm dot com 2007-07-09 04:47 ------- Subject: Re: Kprobes marked EXPERIMENTAL > 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? I agree that the tag needs to be granular. On the kprobes front, we need to take a call on an arch basis. I'd say, based on testing over the past couple of years, the EXPERIMENTAL tag can be removed from i386, x86_64, powerpc and IA64. Arch maintainers of sparc64, avr32 and s390 need to take a similar call. Ananth -- 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.