Re: [PATCH] new irq tracer

[Frank Ch. Eigler]

Hi -

On Wed, Feb 18, 2009 at 10:46:20PM +0100, Peter Zijlstra wrote:
> [...]
> How useful is that return value?

"somewhat"?

> Much of the other data is already available, /proc/interrupts will
> happily tell you the source of your interrupt storm. The irq-off
> latency tracer will tell you if stuff takes too much time, the graph
> tracer can tell you what is taking how much time.

Doesn't it seem like this is too much work to have answer a simple if
particular question?

> I really am having a difficult time seeing the use in such narrow
> tracers.

Part of the problem may come from defining "tracers" as something
limited to ftrace engines.  Once such tracepoints are in the kernel,
more powerful analytical tools may be attached to them.


- FChE
--
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/