From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756890AbZERQXN (ORCPT ); Mon, 18 May 2009 12:23:13 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753842AbZERQXE (ORCPT ); Mon, 18 May 2009 12:23:04 -0400 Received: from hrndva-omtalb.mail.rr.com ([71.74.56.123]:65099 "EHLO hrndva-omtalb.mail.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751062AbZERQXD (ORCPT ); Mon, 18 May 2009 12:23:03 -0400 Date: Mon, 18 May 2009 12:23:01 -0400 (EDT) From: Steven Rostedt X-X-Sender: rostedt@gandalf.stny.rr.com To: David Smith cc: Jon Masters , linux-kernel Subject: Re: [tracing] ring_buffer question In-Reply-To: <4A1185B9.8050301@redhat.com> Message-ID: References: <1242594505.6327.3.camel@localhost.localdomain> <1242607182.6327.8.camel@localhost.localdomain> <4A1185B9.8050301@redhat.com> User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 18 May 2009, David Smith wrote: > Jon Masters wrote: > > [thinking out loud] Does the global disable stuff also disable other > > non-tracing ring buffers? > > I believe it does. If I'm correct, I think it would be a good idea to > make that an ftrace-disable feature, not a general ring buffer disable > feature. We can do that when we get more users of the ring buffer and we find it makes sense. -- Steve