From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: "Masami Hiramatsu" <mhiramat@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Clément Léger" <cleger@rivosinc.com>,
"Atish Patra" <atishp@rivosinc.com>
Subject: Re: [for-linus][PATCH 2/4] tracing: relax trace_event_eval_update() execution with cond_resched()
Date: Sat, 30 Sep 2023 16:41:05 -0400 [thread overview]
Message-ID: <20230930164105.534e7400@rorschach.local.home> (raw)
In-Reply-To: <20230930203821.632661639@goodmis.org>
[ The problem with sending email with quilt. It doesn't handle UTF-8 well :-/ ]
On Sat, 30 Sep 2023 16:32:15 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> From: =?UTF-8?q?Cl=C3=A9ment=20L=C3=A9ger?= <cleger@rivosinc.com>
>
> 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 <mhiramat@kernel.org>
> Signed-off-by: Clément Léger <cleger@rivosinc.com>
> Tested-by: Atish Patra <atishp@rivosinc.com>
> Reviewed-by: Atish Patra <atishp@rivosinc.com>
> Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
> ---
> kernel/trace/trace_events.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/kernel/trace/trace_events.c b/kernel/trace/trace_events.c
> index 91951d038ba4..f49d6ddb6342 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);
> }
next prev parent reply other threads:[~2023-09-30 20:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 20:32 [for-linus][PATCH 0/4] tracing: Fixes for v6.6-rc3 Steven Rostedt
2023-09-30 20:32 ` [for-linus][PATCH 1/4] ring-buffer: Update "shortest_full" in polling Steven Rostedt
2023-09-30 20:32 ` [for-linus][PATCH 4/4] eventfs: Test for dentries array allocated in eventfs_release() Steven Rostedt
[not found] ` <20230930203821.632661639@goodmis.org>
2023-09-30 20:41 ` Steven Rostedt [this message]
[not found] ` <20230930203821.843544914@goodmis.org>
2023-09-30 20:41 ` [for-linus][PATCH 3/4] tracing/user_events: Align set_bit() address for all archs Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230930164105.534e7400@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=atishp@rivosinc.com \
--cc=cleger@rivosinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®