[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87mv9hqwt8.fsf@linux.intel.com>
Date: Fri, 09 Jun 2017 13:28:51 +0300
From: Felipe Balbi <felipe.balbi@...ux.intel.com>
To: Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Steven Rostedt <rostedt@...dmis.org>,
Ingo Molnar <mingo@...hat.com>
Cc: Linux USB <linux-usb@...r.kernel.org>,
linux-kernel@...r.kernel.org,
Chunyan Zhang <zhang.chunyan@...aro.org>
Subject: Re: [PATCH] usb: gadget: functions: add ftrace export over USB
Felipe Balbi <felipe.balbi@...ux.intel.com> writes:
> 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.
>
> Signed-off-by: Felipe Balbi <felipe.balbi@...ux.intel.com>
> ---
>
> I wanted to take this through the gadget tree, but there is a
> dependency with a previous patch of mine adding and extra argument to
> the ->write() function. Hoping someone else will take it.
just as an extra note here. In order for this to be really useful, it
would be nice to be able to control what is going to be traced over USB
as well, but that means exporting a few extra functions to GPL drivers.
Would that be okay? I could have a set of vendor-specific control
requests to set buffer size and to read/write ftrace filter functions.
The idea is that things like e.g. Android SDK could rely on this on
debug builds and the SDK itself would make sure to keep a copy of
vmlinux around to processing of the data coming through USB.
--
balbi
Download attachment "signature.asc" of type "application/pgp-signature" (833 bytes)
Powered by blists - more mailing lists