From: Steven Rostedt <rostedt@goodmis.org>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: Kalle Valo <kvalo@qca.qualcomm.com>,
Johannes Berg <johannes@sipsolutions.net>,
Xenia Ragiadakou <burzalodowa@gmail.com>,
OPW Kernel Interns List <opw-kernel-interns@googlegroups.com>,
linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org,
linux-trace-users@vger.kernel.org, Jiri Olsa <jolsa@redhat.com>
Subject: Re: Help adding trace events to xHCI
Date: Fri, 12 Jul 2013 12:55:43 -0400 [thread overview]
Message-ID: <1373648143.17876.98.camel@gandalf.local.home> (raw)
In-Reply-To: <20130712164104.GA15531@xanatos>
On Fri, 2013-07-12 at 09:41 -0700, Sarah Sharp wrote:
> On Fri, Jul 12, 2013 at 07:25:59AM +0300, Kalle Valo wrote:
> Thanks for the suggestion. I'm not familiar with all the userspace
> tools for trace events, so I didn't know about the command parser. Is
> there documentation or a list of resources for all the userspace trace
> event plugins? If so, can you give us a pointer to it?
>
Currently the plugins only exist in trace-cmd. But there's going to be
work done to get them into the kernel tools directory. I was just
talking with Jiri about this today. Perf will require it.
trace-cmd repo is here:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
-- Steve
next prev parent reply other threads:[~2013-07-12 16:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51DB0257.1010709@gmail.com>
2013-07-11 16:20 ` Help adding trace events to xHCI Sarah Sharp
2013-07-11 17:08 ` Arend van Spriel
2013-07-11 17:08 ` Johannes Berg
2013-07-11 19:00 ` Sarah Sharp
2013-07-12 4:25 ` Kalle Valo
2013-07-12 16:41 ` Sarah Sharp
2013-07-12 16:55 ` Steven Rostedt [this message]
2013-07-15 13:47 ` Jiri Olsa
2013-07-12 17:08 ` Mathieu Desnoyers
2013-07-12 19:35 ` Mark Wielaard
2013-07-15 12:55 ` Mathieu Desnoyers
2013-07-12 18:59 ` Kalle Valo
2013-07-26 9:16 ` Johannes Berg
2013-07-11 19:29 ` Steven Rostedt
2013-07-26 9:19 ` Johannes Berg
2013-07-26 12:28 ` Steven Rostedt
2013-07-26 13:06 ` Johannes Berg
2013-07-26 13:17 ` Steven Rostedt
2013-07-26 13:45 ` Johannes Berg
2013-07-26 14:05 ` Steven Rostedt
2013-07-12 4:23 ` Kalle Valo
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=1373648143.17876.98.camel@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=burzalodowa@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=jolsa@redhat.com \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-trace-users@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=opw-kernel-interns@googlegroups.com \
--cc=sarah.a.sharp@linux.intel.com \
/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;
as well as URLs for NNTP newsgroup(s).