[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0905181300450.21785@gandalf.stny.rr.com>
Date: Mon, 18 May 2009 13:03:01 -0400 (EDT)
From: Steven Rostedt <rostedt@...dmis.org>
To: David Smith <dsmith@...hat.com>
cc: Jon Masters <jonathan@...masters.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [tracing] ring_buffer question
On Mon, 18 May 2009, David Smith wrote:
> Steven Rostedt wrote:
> > 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.
>
> It appears that oprofile is already using the ring buffer. With Jon's
> stuff as a 2nd non-ftrace-user, doesn't it make sense now?
I guess it might also be something that we want to consider too. That is,
the "tracing_off" is a nice feature for all users of the ring buffer. Once
can stop and start the oprofiler buffer via the user interface
"tracing_on" as well. Is this something that would also be useful? If we
make it "ftrace only" then oprofile loses this feature.
Now we could make a file for every registered user of the ring buffer.
Well, not every registered user, but have the user register their own
"tracing_on" file.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists