summaryrefslogtreecommitdiffstats
path: root/kernel/trace/trace_syscalls.c
diff options
context:
space:
mode:
authorSteven Rostedt (Red Hat) <rostedt@goodmis.org>2014-08-05 23:19:38 +0200
committerSteven Rostedt <rostedt@goodmis.org>2014-09-10 16:48:44 +0200
commite1effa0144a1ddf5b456c388ffaf784f3c5163fd (patch)
treec169e93553bf595d5c1f3bbd7f25d56ed0f27b2d /kernel/trace/trace_syscalls.c
parentftrace: Grab any ops for a rec for enabled_functions output (diff)
downloadlinux-e1effa0144a1ddf5b456c388ffaf784f3c5163fd.tar.xz
linux-e1effa0144a1ddf5b456c388ffaf784f3c5163fd.zip
ftrace: Annotate the ops operation on update
Add three new flags for ftrace_ops: FTRACE_OPS_FL_ADDING FTRACE_OPS_FL_REMOVING FTRACE_OPS_FL_MODIFYING These will be set for the ftrace_ops when they are first added to the function tracing, being removed from function tracing or just having their functions changed from function tracing, respectively. This will be needed to remove the tramp_hash, which can grow quite big. The tramp_hash is used to note what functions a ftrace_ops is using a trampoline for. Denoting which ftrace_ops is being modified, will allow us to use the ftrace_ops hashes themselves, which are much smaller as they have a global flag to denote if a ftrace_ops is tracing all functions, as well as a notrace hash if the ftrace_ops is tracing all but a few. The tramp_hash just creates a hash item for every function, which can go into the 10s of thousands if all functions are using the ftrace_ops trampoline. Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Diffstat (limited to 'kernel/trace/trace_syscalls.c')
0 files changed, 0 insertions, 0 deletions