From: "Paul E. McKenney" <paulmck@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@redhat.com, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
linux-kernel@vger.kernel.org
Subject: Re: Pinning down a blocked task to extract diagnostics
Date: Thu, 5 Mar 2020 06:22:45 -0800 [thread overview]
Message-ID: <20200305142245.GB2935@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200305081337.GA2619@hirez.programming.kicks-ass.net>
On Thu, Mar 05, 2020 at 09:13:37AM +0100, Peter Zijlstra wrote:
> On Thu, Mar 05, 2020 at 09:07:55AM +0100, Peter Zijlstra wrote:
> > On Wed, Mar 04, 2020 at 04:50:49PM -0800, Paul E. McKenney wrote:
> > > Hello!
> > >
> > > Suppose that I need to extract diagnostics information from a blocked
> > > task, but that I absolutely cannot tolerate this task awakening in the
> > > midst of this extraction process. Is the following code the right way
> > > to make this work given a task "t"?
> > >
> > > raw_spin_lock_irq(&t->pi_lock);
> > > if (t->on_rq) {
> > > /* Task no longer blocked, so ignore it. */
> > > } else {
> > > /* Extract consistent diagnostic information. */
> > > }
> > > raw_spin_unlock_irq(&t->pi_lock);
> > >
> > > It looks like all the wakeup paths acquire ->pi_lock, but I figured I
> > > should actually ask...
> >
> > Close, the thing pi_lock actually guards is the t->state transition *to*
> > TASK_WAKING/TASK_RUNNING, so something like this:
>
> Almost, we must indeed also check ->on_rq, otherwise it might change the
> state back itself.
>
> >
> > raw_spin_lock_irq(&t->pi_lock);
> > switch (t->state) {
> > case TASK_RUNNING:
> > case TASK_WAKING:
> > /* ignore */
> > break;
> >
> > default:
> if (t->on_rq)
> break;
>
> > /* Extract consistent diagnostic information. */
> > break;
> > }
> > raw_spin_unlock_irq(&t->pi_lock);
> >
> > ought to work. But if you're going to do this, please add a reference to
> > that code in a comment on top of try_to_wake_up(), such that we can
> > later find all the code that relies on this.
How about if I add something like this, located right by try_to_wake_up()?
bool try_to_keep_sleeping(struct task_struct *t)
{
raw_spin_lock_irq(&t->pi_lock);
switch (t->state) {
case TASK_RUNNING:
case TASK_WAKING:
raw_spin_unlock_irq(&t->pi_lock);
return false;
default:
if (t->on_rq) {
raw_spin_unlock_irq(&t->pi_lock);
return false;
}
/* OK to extract consistent diagnostic information. */
return true;
}
/* NOTREACHED */
}
Then a use might look like this:
if (try_to_keep_sleeping(t))
/* Extract consistent diagnostic information. */
raw_spin_unlock_irq(&t->pi_lock);
} else {
/* Woo-hoo! It started running again!!! */
}
Is there a better way to approach this?
Thanx, Paul
next prev parent reply other threads:[~2020-03-05 14:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 0:50 Paul E. McKenney
2020-03-05 3:52 ` Steven Rostedt
2020-03-05 4:25 ` Paul E. McKenney
2020-03-05 8:07 ` Peter Zijlstra
2020-03-05 8:13 ` Peter Zijlstra
2020-03-05 14:01 ` Steven Rostedt
2020-03-05 14:22 ` Paul E. McKenney [this message]
2020-03-05 14:28 ` Steven Rostedt
2020-03-05 15:36 ` Paul E. McKenney
2020-03-06 1:40 ` Paul E. McKenney
2020-03-06 16:56 ` Steven Rostedt
2020-03-06 21:01 ` Paul E. McKenney
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=20200305142245.GB2935@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.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®