From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Scott Wood <swood@redhat.com>
Cc: linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
"Paul E . McKenney" <paulmck@linux.ibm.com>,
Joel Fernandes <joel@joelfernandes.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Clark Williams <williams@redhat.com>
Subject: Re: [PATCH RT v2 2/3] sched: migrate_enable: Use sleeping_lock to indicate involuntary sleep
Date: Fri, 23 Aug 2019 18:20:24 +0200 [thread overview]
Message-ID: <20190823162024.47t7br6ecfclzgkw@linutronix.de> (raw)
In-Reply-To: <20190821231906.4224-3-swood@redhat.com>
On 2019-08-21 18:19:05 [-0500], Scott Wood wrote:
> Without this, rcu_note_context_switch() will complain if an RCU read
> lock is held when migrate_enable() calls stop_one_cpu().
>
> Signed-off-by: Scott Wood <swood@redhat.com>
> ---
> v2: Added comment.
>
> If my migrate disable changes aren't taken, then pin_current_cpu()
> will also need to use sleeping_lock_inc() because calling
> __read_rt_lock() bypasses the usual place it's done.
>
> include/linux/sched.h | 4 ++--
> kernel/rcu/tree_plugin.h | 2 +-
> kernel/sched/core.c | 8 ++++++++
> 3 files changed, 11 insertions(+), 3 deletions(-)
>
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -7405,7 +7405,15 @@ void migrate_enable(void)
> unpin_current_cpu();
> preempt_lazy_enable();
> preempt_enable();
> +
> + /*
> + * sleeping_lock_inc suppresses a debug check for
> + * sleeping inside an RCU read side critical section
> + */
> + sleeping_lock_inc();
> stop_one_cpu(task_cpu(p), migration_cpu_stop, &arg);
> + sleeping_lock_dec();
this looks like an ugly hack. This sleeping_lock_inc() is used where we
actually hold a sleeping lock and schedule() which is okay. But this
would mean we hold a RCU lock and schedule() anyway. Is that okay?
> +
> return;
> }
> }
Sebastian
next prev parent reply other threads:[~2019-08-23 16:20 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-21 23:19 [PATCH RT v2 0/3] RCU fixes Scott Wood
2019-08-21 23:19 ` [PATCH RT v2 1/3] rcu: Acquire RCU lock when disabling BHs Scott Wood
2019-08-21 23:33 ` Paul E. McKenney
2019-08-22 13:39 ` Joel Fernandes
2019-08-22 15:27 ` Paul E. McKenney
2019-08-23 1:50 ` Joel Fernandes
2019-08-23 2:11 ` Paul E. McKenney
2019-08-23 3:23 ` Scott Wood
2019-08-23 12:30 ` Paul E. McKenney
2019-08-23 16:17 ` Sebastian Andrzej Siewior
2019-08-23 19:46 ` Scott Wood
2019-08-26 15:59 ` Sebastian Andrzej Siewior
2019-08-26 23:21 ` Scott Wood
2019-08-23 2:36 ` Scott Wood
2019-08-23 2:54 ` Paul E. McKenney
2019-08-21 23:19 ` [PATCH RT v2 2/3] sched: migrate_enable: Use sleeping_lock to indicate involuntary sleep Scott Wood
2019-08-21 23:35 ` Paul E. McKenney
2019-08-23 1:21 ` Scott Wood
2019-08-23 16:20 ` Sebastian Andrzej Siewior [this message]
2019-08-23 19:28 ` Scott Wood
2019-08-24 3:10 ` Joel Fernandes
2019-08-26 15:25 ` Sebastian Andrzej Siewior
2019-08-26 16:29 ` Paul E. McKenney
2019-08-26 17:49 ` Scott Wood
2019-08-26 18:12 ` Paul E. McKenney
2019-08-27 9:23 ` Sebastian Andrzej Siewior
2019-08-27 13:08 ` Joel Fernandes
2019-08-27 15:58 ` Paul E. McKenney
2019-08-27 16:06 ` Joel Fernandes
2019-08-27 15:53 ` Paul E. McKenney
2019-08-28 9:27 ` Sebastian Andrzej Siewior
2019-08-28 12:54 ` Paul E. McKenney
2019-08-28 13:14 ` Sebastian Andrzej Siewior
2019-08-28 13:59 ` Joel Fernandes
2019-08-28 15:51 ` Paul E. McKenney
2019-08-28 15:50 ` Paul E. McKenney
2019-08-21 23:19 ` [PATCH RT v2 3/3] rcu: Disable use_softirq on PREEMPT_RT Scott Wood
2019-08-21 23:40 ` Paul E. McKenney
2019-08-23 16:32 ` Sebastian Andrzej Siewior
2019-08-22 13:59 ` Joel Fernandes
2019-08-22 15:29 ` Paul E. McKenney
2019-08-22 19:31 ` Scott Wood
2019-08-23 0:52 ` Joel Fernandes
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=20190823162024.47t7br6ecfclzgkw@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=joel@joelfernandes.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=paulmck@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=swood@redhat.com \
--cc=tglx@linutronix.de \
--cc=williams@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).