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

[Seiji Aguchi]

>Well ftrace is a whole subsystem that includes the function tracer and also an interface
>for tracepoints in debugfs. I was rather suggesting the latter one. This is a good
>choice for background tracing. And it supports stacktraces. If those generate too much
>overhead perhaps you can tune the number of entries in the stacktrace, I don't remember
>if we can do that currently but this can be an interesting feature.

I would like to periodically check which function call is executed
rather than seeing stacktrace.

AFAIK, purpose of stack tracing is showing where the biggest use of the stack takes place.
I don't think stack tracing achieves my goal.

Rip in local timer interrupt is more accurate information 
for achieving my goal than stacktrace

>
>What are you using currently for the background tracing?

Currently, we are using SystemTap in customer's system.
So, I would like to use this tracepoint with SystemTap.

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