RE: [PATCH 2/2] trace,x86: Add x86 irq vector entry/exit tracepoints

[Seiji Aguchi]

Thank you for giving me a comment.
Unfortunately, neither "perf record" nor "ftrace" works for me.

>What about using perf for that?
>
>Just run:
>
>	perf record -ag
>	^C
>	perf report
>
>And you should find in the callchains some informations about where your CPUs
>are spending time.
>
>If you system is too slow for that 

When system is too slow, user command such as "perf record" may not work.

>but you're doing background tracing with
>ftrace, you can use stacktrace with ftrace.

Actually, We're doing background tracing in our customer's system rather than kernel debugging. 
Ftrace doesn't work for me because it checks the size of the stack at every function call.
Our customers are seriously concerned about its overhead.

For reducing the overhead, I need tracepoints so we can hook minimal function calls.

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