hi Ming >> >> in http://permalink.gmane.org/gmane.linux.usb.general/89363 >> >> I have some questions about this patch. >> 1. is there patch or kernel config I can use to measure man/avage usb >> irq time consuming like the above link show > > One approach I like to use is trace event. Would you please let us how to to use trace event for calculate max/average usb irq time? > >> >> 2. I see this patch is roll back in commit >> "c04ee4b1136e462722567cf6e76bb35a181574a7" and intend to be ready in >> 3.13-rc1 >> Is there special reason why we need to roll back? > > Yes, the revert revert can enable to run completion handler in BH, > isn't that what you need? YES, what I need is try to see whether my problem will be solved if running completion handlers in BH. At beginning, the "revert" let me think there are something wrong after we put completion in BH. And we need to revert it back to "put completion in irq" so the revert mean "put completion in BH", right? > > But actually the local interrupt is still disabled during completion > because we need to convert spin_lock in all current usb drivers > to spin_lock_irqsave() first. Would you please let me know the function or source you mentioned? BTW, why I cannot see xhci add HCD_BH? is there some reason xhci cannot put completion in BH? thanks for your kind help, -- 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
