diff options
author | 2020-10-28 08:19:24 -0400 | |
---|---|---|
committer | 2020-11-10 20:39:36 -0500 | |
commit | 60602cb549f1965a7edbc96026760dfb93911fab (patch) | |
tree | a20295d7f8aa5216ff7a504d313b79f52adab181 /include/linux/ftrace.h | |
parent | ftrace: Add recording of functions that caused recursion (diff) | |
download | linux-60602cb549f1965a7edbc96026760dfb93911fab.tar.gz linux-60602cb549f1965a7edbc96026760dfb93911fab.tar.bz2 linux-60602cb549f1965a7edbc96026760dfb93911fab.zip |
fgraph: Make overruns 4 bytes in graph stack structure
Inspecting the data structures of the function graph tracer, I found that
the overrun value is unsigned long, which is 8 bytes on a 64 bit machine,
and not only that, the depth is an int (4 bytes). The overrun can be simply
an unsigned int (4 bytes) and pack the ftrace_graph_ret structure better.
The depth is moved up next to the func, as it is used more often with func,
and improves cache locality.
Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'include/linux/ftrace.h')
-rw-r--r-- | include/linux/ftrace.h | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/include/linux/ftrace.h b/include/linux/ftrace.h index 806196345c3f..8dde9c17aaa5 100644 --- a/include/linux/ftrace.h +++ b/include/linux/ftrace.h @@ -864,11 +864,11 @@ struct ftrace_graph_ent { */ struct ftrace_graph_ret { unsigned long func; /* Current function */ + int depth; /* Number of functions that overran the depth limit for current task */ - unsigned long overrun; + unsigned int overrun; unsigned long long calltime; unsigned long long rettime; - int depth; } __packed; /* Type of the callback handlers for tracing function graph*/ |