From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>,
Linux USB <linux-usb@vger.kernel.org>,
linux-kernel@vger.kernel.org,
Chunyan Zhang <zhang.chunyan@linaro.org>
Subject: Re: [PATCH] usb: gadget: functions: add ftrace export over USB
Date: Fri, 09 Jun 2017 17:05:52 +0300 [thread overview]
Message-ID: <878tl1qmrj.fsf@linux.intel.com> (raw)
In-Reply-To: <20170609100233.414b4b38@gandalf.local.home>
[-- Attachment #1: Type: text/plain, Size: 1286 bytes --]
Hi,
Steven Rostedt <rostedt@goodmis.org> writes:
> On Fri, 9 Jun 2017 09:13:27 +0300
> Felipe Balbi <felipe.balbi@linux.intel.com> wrote:
>
>> Allow for ftrace data to be exported over a USB Gadget
>> Controller. With this, we have a potentially very fast pipe for
>> transmitting ftrace data to a Host PC for further analysis.
>>
>> Note that in order to decode the data, one needs access to kernel
>> symbols in order to convert binary data into function names and what
>> not.
>>
>
> Can you please explain what this is in a bit more detail. I have no
> idea what you are trying to accomplish.
this is just another ftrace export. Just like STM
(drivers/hwtracing/stm/ftrace.c), but I'm making use of a USB Peripheral
Controller that may be available.
> Also, do you mean ftrace as the internal Linux tracer (which should
> only be called "ftrace" or sometimes "Ftrace" but not "f_trace" or
> "FTrace", that just leads to more confusion.
heh, internal linux ftrace ;-) The driver name (f-trace.c) is just to
follow the convention of USB functions being name f_*.c or f-*.c. I
could call it f-ftrace.c, but seemed unnecessary.
> Or is this to do with http://www.ftrace.com/en/gb, a way to trace
> produce ;-)
heh :-) unlikely
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-06-09 14:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 6:13 [PATCH] usb: gadget: functions: add ftrace export over USB Felipe Balbi
2017-06-09 10:28 ` Felipe Balbi
2017-06-09 11:15 ` Felipe Balbi
2017-07-14 5:52 ` Pratyush Anand
2017-07-14 6:53 ` Felipe Balbi
2017-07-14 21:44 ` Steven Rostedt
2017-06-09 14:02 ` Steven Rostedt
2017-06-09 14:05 ` Felipe Balbi [this message]
2017-06-09 15:07 ` Steven Rostedt
2017-06-10 3:38 ` kbuild test robot
2017-06-12 10:39 ` Felipe Balbi
2017-06-10 4:02 ` kbuild test robot
2017-07-13 11:40 ` Felipe Balbi
2017-07-14 5:31 ` Pratyush Anand
2017-07-14 6:56 ` Felipe Balbi
2019-03-21 9:38 ` Felipe Balbi
2019-03-21 16:37 ` Steven Rostedt
2019-03-22 11:49 ` Felipe Balbi
2019-03-22 12:22 ` Steven Rostedt
2019-03-22 12:27 ` Felipe Balbi
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=878tl1qmrj.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=zhang.chunyan@linaro.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;
as well as URLs for NNTP newsgroup(s).