Hi, Steven Rostedt <rostedt@xxxxxxxxxxx> writes: > On Fri, 9 Jun 2017 09:13:27 +0300 > Felipe Balbi <felipe.balbi@xxxxxxxxxxxxxxx> 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:
signature.asc
Description: PGP signature
