Hello Alan, John,
I had this question from the embedded perspective. printk on occasions
seems to have some overhead which actually dilutes the issue occurrence
frequency. So, just wanted to know if this was not included by choice.
Many Thanks,
~Bala
On 07/19/2012 12:12 AM, Alan Stern wrote:
On Wed, 18 Jul 2012, Balakumar wrote:
Hello All,
I see that there are no tracing options (e.g. traceevents) defined in
the USB subsystem. Like, they have been defined for scsi, scheduler,
workqueues etc (include/trace/events/*). I am fairly new to Linux and I
am trying to study the debugging options available. Just wanted to
understand why such kernel tracing options are not used with USB.
As far as I know, the only reason there aren't any USB tracepoints is
because nobody has ever felt the need to add some.
Alan Stern
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html