Messages in this thread | | | From | Seiji Aguchi <> | Date | Wed, 14 Dec 2011 10:09:11 -0500 | Subject | RE: [PATCH 2/2] trace,x86: Add x86 irq vector entry/exit tracepoints |
| |
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
| |