Re: interrupt overhead on ARM architecture

[Benjamin Herrenschmidt]

On Tue, 2008-07-29 at 00:08 -0700, Alessio Sangalli wrote:
> Iwo Mergler wrote:
> 
> > In other words, you can't even measure the latency on a particular
> > system and then assume it will stay anywhere near constant. Comparing
> > different systems with the same processor core is hopeless.
> 
> Everything makes perfect sense. For this reason, I am willing to do some
> tests on my own platform. How would you suggest to proceed? I would need
> an extremely accurate way to measure time to begin with and then:
> 
> - read that time reference
> - generate an interrupt by placing some data in a device or so
> - reading again that time reference as first thing in the ISR
> - save the result
> 
> - do the above in various scenarios, with different drivers enabled, CPU
> load, etc etc

Do you have some device you can toy with such as an FPGA ? If not, you
can use also a pair of GPIOs hooked up to an oscillo.

Have one GPIO be an interrupt, and the interrupt handler for it toggle
the second GPIO.

Then, stick a push button to the first GPIO and wire it to your
oscilloscope's first input, and the second to the second input, set the
trigger on the first input, and here you go...

Ben.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/