From: Lai Jiangshan <laijs@linux.alibaba.com>
To: paulmck@kernel.org, 20191015102402.1978-1-laijs@linux.alibaba.com
Cc: linux-kernel@vger.kernel.org,
Lai Jiangshan <jiangshanlai@gmail.com>,
Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Joel Fernandes <joel@joelfernandes.org>,
rcu@vger.kernel.org
Subject: Re: [PATCH 6/7] rcu: rename some CONFIG_PREEMPTION to CONFIG_PREEMPT_RCU
Date: Wed, 16 Oct 2019 23:26:23 +0800 [thread overview]
Message-ID: <484d846f-8fbb-ccd2-d66a-a6b48d4a1df4@linux.alibaba.com> (raw)
In-Reply-To: <20191016035407.GB2689@paulmck-ThinkPad-P72>
On 2019/10/16 11:54 上午, Paul E. McKenney wrote:
> On Tue, Oct 15, 2019 at 10:28:48AM +0000, Lai Jiangshan wrote:
>> CONFIG_PREEMPTION and CONFIG_PREEMPT_RCU are always identical,
>> but some code depends on CONFIG_PREEMPTION to access to
>> rcu_preempt functionalitis. This patch changes CONFIG_PREEMPTION
>> to CONFIG_PREEMPT_RCU in these cases.
>>
>> Signed-off-by: Lai Jiangshan <jiangshanlai@gmail.com>
>> Signed-off-by: Lai Jiangshan <laijs@linux.alibaba.com>
>
> I believe that this does not cause problems with Sebastian's patch
> "[PATCH 27/34] rcu: Use CONFIG_PREEMPTION where appropriate", but could
> you please check?
I don't know for which commit the patch "[PATCH 27/34] rcu: Use
CONFIG_PREEMPTION where appropriate" should be applied against
after several tries. But I don't think there will be any conflicts
which this patch by "eye" applying.
Thanks,
Lai
>
> Thanx, Paul
>
>> ---
>> kernel/rcu/tree.c | 4 ++--
>> kernel/rcu/tree_stall.h | 6 +++---
>> 2 files changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c
>> index 7db5ea06a9ed..81eb64fcf5ab 100644
>> --- a/kernel/rcu/tree.c
>> +++ b/kernel/rcu/tree.c
>> @@ -1926,7 +1926,7 @@ rcu_report_unblock_qs_rnp(struct rcu_node *rnp, unsigned long flags)
>> struct rcu_node *rnp_p;
>>
>> raw_lockdep_assert_held_rcu_node(rnp);
>> - if (WARN_ON_ONCE(!IS_ENABLED(CONFIG_PREEMPTION)) ||
>> + if (WARN_ON_ONCE(!IS_ENABLED(CONFIG_PREEMPT_RCU)) ||
>> WARN_ON_ONCE(rcu_preempt_blocked_readers_cgp(rnp)) ||
>> rnp->qsmask != 0) {
>> raw_spin_unlock_irqrestore_rcu_node(rnp, flags);
>> @@ -2294,7 +2294,7 @@ static void force_qs_rnp(int (*f)(struct rcu_data *rdp))
>> mask = 0;
>> raw_spin_lock_irqsave_rcu_node(rnp, flags);
>> if (rnp->qsmask == 0) {
>> - if (!IS_ENABLED(CONFIG_PREEMPTION) ||
>> + if (!IS_ENABLED(CONFIG_PREEMPT_RCU) ||
>> rcu_preempt_blocked_readers_cgp(rnp)) {
>> /*
>> * No point in scanning bits because they
>> diff --git a/kernel/rcu/tree_stall.h b/kernel/rcu/tree_stall.h
>> index 0b75426ebb3e..55f9b84790d3 100644
>> --- a/kernel/rcu/tree_stall.h
>> +++ b/kernel/rcu/tree_stall.h
>> @@ -163,7 +163,7 @@ static void rcu_iw_handler(struct irq_work *iwp)
>> //
>> // Printing RCU CPU stall warnings
>>
>> -#ifdef CONFIG_PREEMPTION
>> +#ifdef CONFIG_PREEMPT_RCU
>>
>> /*
>> * Dump detailed information for all tasks blocking the current RCU
>> @@ -215,7 +215,7 @@ static int rcu_print_task_stall(struct rcu_node *rnp)
>> return ndetected;
>> }
>>
>> -#else /* #ifdef CONFIG_PREEMPTION */
>> +#else /* #ifdef CONFIG_PREEMPT_RCU */
>>
>> /*
>> * Because preemptible RCU does not exist, we never have to check for
>> @@ -233,7 +233,7 @@ static int rcu_print_task_stall(struct rcu_node *rnp)
>> {
>> return 0;
>> }
>> -#endif /* #else #ifdef CONFIG_PREEMPTION */
>> +#endif /* #else #ifdef CONFIG_PREEMPT_RCU */
>>
>> /*
>> * Dump stacks of all tasks running on stalled CPUs. First try using
>> --
>> 2.20.1
>>
next prev parent reply other threads:[~2019-10-16 15:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 10:28 [PATCH 3/7] rcu: trace_rcu_utilization() paired Lai Jiangshan
2019-10-15 10:28 ` [PATCH 4/7] rcu: remove the declaration of call_rcu() in tree.h Lai Jiangshan
2019-10-16 3:47 ` Paul E. McKenney
2019-10-15 10:28 ` [PATCH 5/7] rcu: move gp_state_names[] and gp_state_getname() to tree_stall.h Lai Jiangshan
2019-10-15 10:28 ` [PATCH 6/7] rcu: rename some CONFIG_PREEMPTION to CONFIG_PREEMPT_RCU Lai Jiangshan
2019-10-16 3:54 ` Paul E. McKenney
2019-10-16 15:26 ` Lai Jiangshan [this message]
2019-10-17 3:00 ` Paul E. McKenney
2019-10-15 10:28 ` [PATCH 7/7] rcu: splite tasks_rcu to tasks.c Lai Jiangshan
2019-10-16 3:40 ` [PATCH 3/7] rcu: trace_rcu_utilization() paired 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=484d846f-8fbb-ccd2-d66a-a6b48d4a1df4@linux.alibaba.com \
--to=laijs@linux.alibaba.com \
--cc=20191015102402.1978-1-laijs@linux.alibaba.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome