From: "Luis Claudio R. Goncalves" <lgoncalv@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Clark Williams <clrkwllms@kernel.org>, Tejun Heo <tj@kernel.org>,
David Vernet <dvernet@meta.com>, Barret Rhoden <brho@google.com>,
Josh Don <joshdon@google.com>, Crystal Wood <crwood@redhat.com>,
linux-kernel@vger.kernel.org, linux-rt-devel@lists.linux.dev,
Juri Lelli <juri.lelli@redhat.com>
Subject: Re: [PATCH] sched: do not call __put_task_struct() on rt if pi_blocked_on is set
Date: Wed, 9 Apr 2025 13:27:12 -0300 [thread overview]
Message-ID: <Z_af4PF18ocF0bBW@uudg.org> (raw)
In-Reply-To: <20250409114330.1444221e@gandalf.local.home>
On Wed, Apr 09, 2025 at 11:43:30AM -0400, Steven Rostedt wrote:
> On Tue, 8 Apr 2025 21:27:37 -0300
> "Luis Claudio R. Goncalves" <lgoncalv@redhat.com> wrote:
>
> > {
> > + bool defer = false;
> > +
> > if (!refcount_dec_and_test(&t->usage))
> > return;
> >
> > /*
> > * In !RT, it is always safe to call __put_task_struct().
> > - * Under RT, we can only call it in preemptible context.
> > + * Under RT, we can only call it in preemptible context,
> > + * when not blocked on a PI chain.
> > */
> > - if (!IS_ENABLED(CONFIG_PREEMPT_RT) || preemptible()) {
> > +#ifdef CONFIG_PREEMPT_RT
> > + if (!preemptible() || current->pi_blocked_on)
> > + defer = true;
> > +#endif
>
> Why add the ugly #ifdef back?
>
> if (!IS_ENABLED(CONFIG_PREEMPT_RT) ||
> (preemptible() && !current->pi_blocked_on)) {
I had to add the #ifdef to avoid the build failing if CONFIG_RT_MUTEXES is
not set. I do know SMP, FUTEX, I2C, PSTORE and a few more things depend on
CONFIG_RT_MUTEXES being enabled, but I opted for being thorough.
I would be more than glad getting rid of the #ifdef and simplifying the patch
if that possible build failure is not a case to worry about, if RT_MUTEXES are
always enabled nowadays.
Luis
> -- Steve
>
> > +
> > + if (!defer) {
> > static DEFINE_WAIT_OVERRIDE_MAP(put_task_map, LD_WAIT_SLEEP);
> >
> >
>
---end quoted text---
next prev parent reply other threads:[~2025-04-09 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 0:27 Luis Claudio R. Goncalves
2025-04-09 15:43 ` Steven Rostedt
2025-04-09 16:27 ` Luis Claudio R. Goncalves [this message]
2025-04-09 16:39 ` Steven Rostedt
2025-04-09 17:02 ` Luis Claudio R. Goncalves
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=Z_af4PF18ocF0bBW@uudg.org \
--to=lgoncalv@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=brho@google.com \
--cc=clrkwllms@kernel.org \
--cc=crwood@redhat.com \
--cc=dvernet@meta.com \
--cc=joshdon@google.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-devel@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=tj@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®