G'Day, The funciton_graph profiler is great for investigating child calls for a given function, but I'd often like to see ancestry. Especially since I'm using it with tracing_thresh, where I'd like to trace slow function calls and their ancestry. The stacktrace option doesn't currently seem supported. For example: # echo mutex_lock > set_ftrace_filter # echo mutex_lock > set_graph_function # echo 10 > tracing_thresh # echo function_graph > current_tracer # echo 1 > options/stacktrace # cat trace_pipe 0) + 12.006 us | } /* mutex_lock */ 1) + 14.947 us | } /* mutex_lock */ ------------------------------------------ 0) <...>-20134 => <...>-20142 ------------------------------------------ 0) + 14.898 us | } /* mutex_lock */ ------------------------------------------ 0) <...>-20142 => <...>-20170 ------------------------------------------ 0) + 12.420 us | } /* mutex_lock */ # grep stack trace_options stacktrace nouserstacktrace I wasn't thinking of mutex_lock() in particular, but you can imagine any generic function where a latency outlier is interesting, given the stack trace. Thanks, Brendan -- To unsubscribe from this list: send the line "unsubscribe linux-trace-users" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|