On Tue, 14 Jan 2025 10:12:02 -0500 Steven Rostedt <[email protected]> wrote:
> From: Steven Rostedt <[email protected]> > > The function graph tracer now calculates the calltime internally and for > each instance. If there are two instances that are running function graph > tracer and are tracing the same functions, the timings of the length of > those functions may be slightly different: > > # trace-cmd record -B foo -p function_graph -B bar -p function_graph sleep 5 > # trace-cmd report > [..] > bar: sleep-981 [000] ...1. 1101.109027: funcgraph_entry: > 0.764 us | mutex_unlock(); (ret=0xffff8abcc256c300) > foo: sleep-981 [000] ...1. 1101.109028: funcgraph_entry: > 0.748 us | mutex_unlock(); (ret=0xffff8abcc256c300) > bar: sleep-981 [000] ..... 1101.109029: funcgraph_exit: > 2.456 us | } (ret=0xffff8abcc256c300) > foo: sleep-981 [000] ..... 1101.109029: funcgraph_exit: > 2.403 us | } (ret=0xffff8abcc256c300) > bar: sleep-981 [000] d..1. 1101.109031: funcgraph_entry: > 0.844 us | fpregs_assert_state_consistent(); (ret=0x0) > foo: sleep-981 [000] d..1. 1101.109032: funcgraph_entry: > 0.803 us | fpregs_assert_state_consistent(); (ret=0x0) > I added: Link: https://lore.kernel.org/all/[email protected]/ Suggested-by: Masami Hiramatsu <[email protected]> To this as well. -- Steve > Signed-off-by: Steven Rostedt (Google) <[email protected]> > --- > Documentation/trace/ftrace.rst | 6 ++++++ > 1 file changed, 6 insertions(+)
