ring-buffer: no preempt for sched_clock()
authorSteven Rostedt <rostedt@goodmis.org>
Wed, 12 Nov 2008 05:01:27 +0000 (00:01 -0500)
committerIngo Molnar <mingo@elte.hu>
Wed, 12 Nov 2008 10:23:36 +0000 (11:23 +0100)
commit47e74f2ba8fbf9fb1378e2524e6cfdc2fb37f160
tree7d49bf91e5409c432b259c26fcadff0450dffe43
parentc1e7abbc7afc97367cd77c8f2895c2169a8f9c87
ring-buffer: no preempt for sched_clock()

Impact: disable preemption when calling sched_clock()

The ring_buffer_time_stamp still uses sched_clock as its counter.
But it is a bug to call it with preemption enabled. This requirement
should not be pushed to the ring_buffer_time_stamp callers, so
the ring_buffer_time_stamp needs to disable preemption when calling
sched_clock.

Signed-off-by: Steven Rostedt <srostedt@redhat.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
kernel/trace/ring_buffer.c