From: Clément Léger Date: Fri, 29 Sep 2023 19:16:37 +0000 (+0200) Subject: tracing: relax trace_event_eval_update() execution with cond_resched() X-Git-Tag: v6.6.7~1809^2~2 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=23cce5f25491968b23fb9c399bbfb25f13870cd9;p=platform%2Fkernel%2Flinux-starfive.git tracing: relax trace_event_eval_update() execution with cond_resched() When kernel is compiled without preemption, the eval_map_work_func() (which calls trace_event_eval_update()) will not be preempted up to its complete execution. This can actually cause a problem since if another CPU call stop_machine(), the call will have to wait for the eval_map_work_func() function to finish executing in the workqueue before being able to be scheduled. This problem was observe on a SMP system at boot time, when the CPU calling the initcalls executed clocksource_done_booting() which in the end calls stop_machine(). We observed a 1 second delay because one CPU was executing eval_map_work_func() and was not preempted by the stop_machine() task. Adding a call to cond_resched() in trace_event_eval_update() allows other tasks to be executed and thus continue working asynchronously like before without blocking any pending task at boot time. Link: https://lore.kernel.org/linux-trace-kernel/20230929191637.416931-1-cleger@rivosinc.com Cc: Masami Hiramatsu Signed-off-by: Clément Léger Tested-by: Atish Patra Reviewed-by: Atish Patra Signed-off-by: Steven Rostedt (Google) --- diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c index 91951d0..f49d6dd 100644 --- a/kernel/trace/trace_events.c +++ b/kernel/trace/trace_events.c @@ -2770,6 +2770,7 @@ void trace_event_eval_update(struct trace_eval_map **map, int len) update_event_fields(call, map[i]); } } + cond_resched(); } up_write(&trace_event_sem); }