ftrace: code consolidation
Status from this message: i've applied your 3 patches to tip/tracing/ftrace:
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | ftrace: ftrace_preempt_disablekernel/ | +48 | 4 replies | |
| 2/3 | ftrace: insert in the ftrace_preempt_disable functionskernel/ kernel/ kernel/ +1 more | +15 | 0 replies | |
| 3/3 | ftrace: function tracer with irqs disabledkernel/ kernel/ | +40 | 5 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] ftrace: code consolidation
[ For 2.6.29 ]
The first two patches makes ftrace function calling and other sensitive tracing use a macro to handle preemption disabling. This removes a lot of duplicate code that works on preventing the scheduler from infinite recursion.
The last patch sets an easy way for the user to either use irq disabling or preemption disabing for the function tracer.
Peter Zijlstra noticed a bit of a trace that was not showing up due to lost traces caused by interrupts when the function tracer was running.
Due to the sensitive nature of the function tracer, it can not allow for recursive tracing, so it needs to disable recursion while it records the trace. But this also means that without disabling interrupts, any interrupt that happens while the trace is happening will be lost from the trace itself.
-- Steve