[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <y0mmyjqji5h.fsf@ton.toronto.redhat.com>
Date: Wed, 06 Aug 2008 11:08:10 -0400
From: fche@...hat.com (Frank Ch. Eigler)
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: prasad@...ux.vnet.ibm.com, linux-kernel@...r.kernel.org,
dwilder@...ibm.com, hch@...radead.org,
Steven Rostedt <rostedt@...dmis.org>,
mathieu.desnoyers@...ymtl.ca
Subject: Re: [Patch 0/2] Renaming 'trace' to 'relay' and enhancements to 'relay'
Andrew Morton <akpm@...ux-foundation.org> writes:
> [...]
>> Please find the patches that enhance the 'trace' infrastructure
>> (available in the -mm tree) and which introduce two new APIs
>> relay_dump() and relay_printk().
>> [...]
> I'm a bit perplexed by these trace patches
> (http://userweb.kernel.org/~akpm/mmotm/broken-out/trace-code [...]
> Is it useful? Will it be useful? [...] I haven't heard much noise
> about it and I'm struggling to justify merging it.
Right.
> Also, it's starting to look somewhat similar to ftrace, which also
> provides sort of high-bandwidth per-cpu channels into userspace for
> tracing purposes.
Perhaps ftrace ought to use this facility for its debugfs-facing bulk
data interface rather than an internal one that cannot be used by
anyone else. Perhaps lttng could use it. Systemtap could. I believe
a grand unification at this level was the idea.
- FChE
--
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