On Friday 04 April 2008, Woodruff, Richard wrote: > For any interested I'm posting a small snippet of what an ARM-OMAP idle > looks like. Having a nice tool can go a long ways. I'm not sure if the > picture will make it, but it's worth a try. Knowing what is out there > for tools is useful. Presumably this is from the CPU trace port, OMAP3 with NO_HZ. Do I read this right: 18 usec tick processing overhead after receiving an IRQ, before even getting to the generic OMAP GPIO irq logic (which then has to dispatch to the real IRQ handler)? Over 5 usec just for updating jiffies64 ... -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
