Re: [PATCH 2/2] ring-buffer: no preempt for sched_clock

[Ingo Molnar]

* Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:

> Impact: disable preemption no 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@xxxxxxxxxx>
> ---
>  kernel/trace/ring_buffer.c |    8 +++++++-
>  1 files changed, 7 insertions(+), 1 deletions(-)

applied to tip/tracing/urgent, thanks Steve!

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/