From: Neeraj Upadhyay <quic_neeraju@quicinc.com>
To: Zqiang <qiang1.zhang@intel.com>, <paulmck@kernel.org>,
<frederic@kernel.org>
Cc: <rcu@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rcu: Add exp QS check in rcu_exp_handler() for no-preemptible expedited RCU
Date: Wed, 22 Jun 2022 17:56:14 +0530 [thread overview]
Message-ID: <de5bac34-7369-4764-bb56-86d3f8de32fa@quicinc.com> (raw)
In-Reply-To: <20220622103549.2840087-1-qiang1.zhang@intel.com>
On 6/22/2022 4:05 PM, Zqiang wrote:
> In CONFIG_PREEMPT=n and CONFIG_PREEMPT_COUNT=y kernel, after a exp
> grace period begins, if detected current CPU enters idle in
> rcu_exp_handler() IPI handler, will immediately report the exp QS of the
> current cpu, at this time, maybe not being in an RCU read-side critical
> section, but need wait until rcu-softirq or sched-clock irq or sched-switch
> occurs on current CPU to check and report exp QS.
>
> This commit add a exp QS check in rcu_exp_handler(), when not being
> in an RCU read-side critical section, report exp QS earlier.
>
> Signed-off-by: Zqiang <qiang1.zhang@intel.com>
> ---
I am a bit unsure on this change. For non-preempt kernel, technically
(and by design) context switch points are considered RCU read side
critical section end? This change, changes that behavior between
CONFIG_PREEMPT_COUNT=y and CONFIG_PREEMPT_COUNT=n case, for
non-preemptive kernels.
However, I could be missing something here, and would wait for Paul's
review.
Thanks
Neeraj
> kernel/rcu/tree_exp.h | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/kernel/rcu/tree_exp.h b/kernel/rcu/tree_exp.h
> index be667583a554..34f08267410f 100644
> --- a/kernel/rcu/tree_exp.h
> +++ b/kernel/rcu/tree_exp.h
> @@ -828,11 +828,14 @@ static void rcu_exp_handler(void *unused)
> {
> struct rcu_data *rdp = this_cpu_ptr(&rcu_data);
> struct rcu_node *rnp = rdp->mynode;
> + bool preempt_bh_disabled =
> + !!(preempt_count() & (PREEMPT_MASK | SOFTIRQ_MASK));
>
> if (!(READ_ONCE(rnp->expmask) & rdp->grpmask) ||
> __this_cpu_read(rcu_data.cpu_no_qs.b.exp))
> return;
> - if (rcu_is_cpu_rrupt_from_idle()) {
> + if (rcu_is_cpu_rrupt_from_idle() ||
> + (IS_ENABLED(CONFIG_PREEMPT_COUNT) && !preempt_bh_disabled)) {
> rcu_report_exp_rdp(this_cpu_ptr(&rcu_data));
> return;
> }
next prev parent reply other threads:[~2022-06-22 12:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 10:35 Zqiang
2022-06-22 12:26 ` Neeraj Upadhyay [this message]
2022-06-22 17:25 ` Boqun Feng
2022-06-22 23:34 ` Zhang, Qiang1
2022-06-22 23:36 ` Zhang, Qiang1
2022-06-23 0:34 ` Paul E. McKenney
2022-06-23 2:15 ` Boqun Feng
2022-06-23 3:23 ` Zhang, Qiang1
2022-06-27 21:41 ` Paul E. McKenney
2022-06-28 4:32 ` Zhang, Qiang1
2022-07-05 19:14 ` Paul E. McKenney
2022-07-06 2:06 ` Zhang, Qiang1
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=de5bac34-7369-4764-bb56-86d3f8de32fa@quicinc.com \
--to=quic_neeraju@quicinc.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=qiang1.zhang@intel.com \
--cc=rcu@vger.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®