Hi Greg,
When it comes to embedded device cases, I feel that the options are just
left with debug messages. It becomes really difficult to debug some SMP
specific issues, thread deadlocks etc. I felt that, using trace events,
we could effectively log some of those specific data without the penalty
of compromising latency which happens with printks.
usbmon is perfect, but USB-centric. The background behind my queries was
that, is there someway we could trace out whats happening in the USB
which also contains the kernel information, like the cpu%d it is
running, the task context etc.
I am fairly new to linux, so please correct me if I got my understanding
wrong :)
Many Thanks,
~Bala
On 07/20/2012 12:18 AM, Greg KH wrote:
On Thu, Jul 19, 2012 at 10:00:12PM +0530, Balakumar wrote:
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.
What does printk have to do with usbmon?
And note, the USB tracing code was added before there was an in-kernel
tracing infrastructure, so that is why it does not take advantage of it.
Does usbmon somehow not work for you?
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
