From: fche@redhat.com (Frank Ch. Eigler)
To: Andrew Morton <akpm@linux-foundation.org>
Cc: prasad@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
dwilder@us.ibm.com, hch@infradead.org,
Steven Rostedt <rostedt@goodmis.org>,
mathieu.desnoyers@polymtl.ca
Subject: Re: [Patch 0/2] Renaming 'trace' to 'relay' and enhancements to 'relay'
Date: Wed, 06 Aug 2008 11:08:10 -0400 [thread overview]
Message-ID: <y0mmyjqji5h.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <20080804152532.9367abff.akpm@linux-foundation.org> (Andrew Morton's message of "Mon, 4 Aug 2008 15:25:32 -0700")
Andrew Morton <akpm@linux-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
next prev parent reply other threads:[~2008-08-06 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 4:04 K.Prasad
2008-08-04 4:07 ` [Patch 1/2] Merging Documentation/trace.txt with Documentation/filesystems/relay.txt K.Prasad
2008-08-04 4:08 ` [Patch 2/2] Renaming lib/trace.[ch] files to kernel/relay_debugfs.[ch] and enhancements K.Prasad
2008-08-13 5:32 ` Andrew Morton
2008-08-13 6:24 ` K.Prasad
2008-08-04 22:25 ` [Patch 0/2] Renaming 'trace' to 'relay' and enhancements to 'relay' Andrew Morton
2008-08-06 15:08 ` Frank Ch. Eigler [this message]
2008-08-08 3:52 ` K.Prasad
2008-08-08 5:38 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=y0mmyjqji5h.fsf@ton.toronto.redhat.com \
--to=fche@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=dwilder@us.ibm.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=prasad@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®