tracing/ftrace: use preempt_enable_no_resched_notrace in ring_buffer_time_stamp()
authorFrederic Weisbecker <fweisbec@gmail.com>
Tue, 16 Dec 2008 21:08:58 +0000 (22:08 +0100)
committerIngo Molnar <mingo@elte.hu>
Tue, 16 Dec 2008 23:26:35 +0000 (00:26 +0100)
commit2c2d7329d8afa9efa3ec24e19a53e7be9d14f242
tree12dd840eef0475e81e0dc8f616229a030d7caae4
parent9dfc3bc7d21864d47797d64b8d531d4dbbc0b618
tracing/ftrace: use preempt_enable_no_resched_notrace in ring_buffer_time_stamp()

Impact: prevent a trace recursion

After some tests with function graph tracer under x86-32, I saw some recursions
caused by ring_buffer_time_stamp() that calls preempt_enable_no_notrace() which
calls preempt_schedule() which is traced itself.

This patch re-enables preemption without rescheduling.

Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
kernel/trace/ring_buffer.c