On Mon, Oct 12, 2009 at 12:00:37PM +0200, Ingo Molnar wrote:
yeah. I have no objection to adding it to include/trace/. Tracepoints
are a fundamentally global business.
Subsystems can opt to hide their tracepoints locally, but it's better to
have a global view about what's out there, so
Hi,
On Fri, 2009-10-09 at 19:45 -0400, Christoph Hellwig wrote:
On Fri, Oct 09, 2009 at 12:01:16PM -0400, Jason Baron wrote:
hi,
I'd like to move the gfs2 tracepoints to the the common
include/trace/events directory along with all of the other trace events.
It makes understanding what
Hi,
On Fri, 2009-10-09 at 12:01 -0400, Jason Baron wrote:
hi,
I'd like to move the gfs2 tracepoints to the the common
include/trace/events directory along with all of the other trace events.
It makes understanding what tracepoints are available easier, and I see
no reason why gfs2 should
Hi,
On Fri, 2009-10-09 at 12:20 -0400, Jason Baron wrote:
On Fri, Oct 09, 2009 at 05:05:19PM +0100, Steven Whitehouse wrote:
Hi,
On Fri, 2009-10-09 at 12:01 -0400, Jason Baron wrote:
hi,
I'd like to move the gfs2 tracepoints to the the common
include/trace/events directory
On Fri, Oct 09, 2009 at 12:01:16PM -0400, Jason Baron wrote:
hi,
I'd like to move the gfs2 tracepoints to the the common
include/trace/events directory along with all of the other trace events.
It makes understanding what tracepoints are available easier, and I see
no reason why gfs2 should
