From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org,
"Masami Hiramatsu (Google)" <mhiramat@kernel.org>,
rcu@vger.kernel.org, kernel-dev@igalia.com, kernel@gpiccoli.net,
"Paul E . McKenney" <paulmck@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH] ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY kernels
Date: Tue, 13 Dec 2022 19:04:41 -0300 [thread overview]
Message-ID: <07b8285c-abfc-dcc6-5a20-b6f8c9bc7e1e@igalia.com> (raw)
In-Reply-To: <20221116153620.353819e9c6acb1bf39adeca2@kernel.org>
On 16/11/2022 03:36, Masami Hiramatsu (Google) wrote:
> On Tue, 15 Nov 2022 17:48:47 -0300
> "Guilherme G. Piccoli" <gpiccoli@igalia.com> wrote:
>
>> The function match_records() may take a while due to a large
>> number of string comparisons, so when in PREEMPT_VOLUNTARY
>> kernels we could face RCU stalls due to that.
>>
>> Add a cond_resched() to prevent that.
>>
>> Suggested-by: Steven Rostedt <rostedt@goodmis.org>
>> Acked-by: Paul E. McKenney <paulmck@kernel.org> # from RCU CPU stall warning perspective
>> Cc: Masami Hiramatsu <mhiramat@kernel.org>
>> Cc: Mark Rutland <mark.rutland@arm.com>
>> Signed-off-by: Guilherme G. Piccoli <gpiccoli@igalia.com>
>
> This looks good to me.
>
> Acked-by: Masami Hiramatsu (Google) <mhiramat@kernel.org>
>
> Thanks!
>
Hi Steve, sorry to annoy, just a regular ping to see if we can get this
into 6.2 (if too late, not a huge deal).
Thanks,
Guilherme
next prev parent reply other threads:[~2022-12-13 22:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-15 20:48 [PATCH] ftrace: Prevent RCU stall on PREEMPT_VOLUNTARY kernels Guilherme G. Piccoli
2022-11-16 6:36 ` Masami Hiramatsu
2022-11-16 12:45 ` Guilherme G. Piccoli
2022-11-22 13:16 ` Guilherme G. Piccoli
2022-11-22 15:49 ` Steven Rostedt
2022-11-22 17:21 ` Guilherme G. Piccoli
2022-12-13 22:04 ` Guilherme G. Piccoli [this message]
2022-12-13 22:34 ` Steven Rostedt
2022-12-13 23:41 ` Guilherme G. Piccoli
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=07b8285c-abfc-dcc6-5a20-b6f8c9bc7e1e@igalia.com \
--to=gpiccoli@igalia.com \
--cc=kernel-dev@igalia.com \
--cc=kernel@gpiccoli.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mhiramat@kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.