Skip to content

ftrace updates

Steven Rostedt lkml 1 version Applied

Status from this message: applied to tip/tracing/ftrace - thanks Steve.

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 1 replyApplied

Patches in v1 Applied

#Subject and filesSizeRepliesApplied
1/2ftrace: do not init module on ftrace disabledkernel/trace/ftrace.c+2 -20 replies
2/2ftrace: add necessary locking for ftrace recordskernel/trace/ftrace.c+30 -140 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/2] ftrace updates

Due to the new mcount recording method, the assumptions about the records that hold the mcount locations have changed. Now we need to protect reading and writing of the records between module load and reading of the debugfs files. There is not much contention here, but they need to be protected none the less.

I simply use the ftrace_lock to accomplish this. The ftrace_lock should never be held under interrupt context so disabling interrupts should not be necessary. I've run this under lockdep and lockdep has not complained.

-- Steve