From: Frederic Weisbecker <frederic@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Zqiang <qiang1.zhang@intel.com>,
quic_neeraju@quicinc.com, joel@joelfernandes.org,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rcu: Fix missing TICK_DEP_MASK_RCU_EXP dependency check
Date: Sat, 7 Jan 2023 22:39:22 +0100 [thread overview]
Message-ID: <Y7nmihQ126cjqEss@lothringen> (raw)
In-Reply-To: <20221221201634.GH4001@paulmck-ThinkPad-P17-Gen-1>
On Wed, Dec 21, 2022 at 12:16:34PM -0800, Paul E. McKenney wrote:
> On Tue, Dec 20, 2022 at 10:16:25PM +0800, Zqiang wrote:
> > This commit add TICK_DEP_MASK_RCU_EXP dependency check in
> > check_tick_dependency(), fix commit df1e849ae4559 ("rcu: Enable
> > tick for nohz_full CPUs slow to provide expedited QS").
> >
> > Signed-off-by: Zqiang <qiang1.zhang@intel.com>
>
> Again, good eyes, thank you!!!
>
> I have queued this for further review and testing, given that it affects
> pretty much only RCU. However, if someone else would rather take it:
>
> Acked-by: Paul E. McKenney <paulmck@kernel.org>
Thanks for picking it up! Please also add the following tags:
Fixes: df1e849ae455 ("rcu: Enable tick for nohz_full CPUs slow to provide expedited QS")
Acked-by: Frederic Weisbecker <frederic@kernel.org>
Thanks!
next prev parent reply other threads:[~2023-01-07 21:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-20 14:16 [PATCH] rcu: Fix missing TICK_DEP_MASK_RCU_EXP dependency check Zqiang
2022-12-21 20:16 ` Paul E. McKenney
2023-01-07 21:39 ` Frederic Weisbecker [this message]
2023-01-09 19:28 ` Paul E. McKenney
[not found] ` <344A2A3B-628E-467C-BBDF-11C3AB63D432@joelfernandes.org>
2023-01-07 22:11 ` Frederic Weisbecker
2023-01-08 2:48 ` Joel Fernandes
2023-01-08 2:55 ` Joel Fernandes
2023-01-08 23:09 ` Frederic Weisbecker
2023-01-09 19:32 ` Paul E. McKenney
2023-01-09 23:55 ` Frederic Weisbecker
2023-01-13 19:25 ` 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=Y7nmihQ126cjqEss@lothringen \
--to=frederic@kernel.org \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=qiang1.zhang@intel.com \
--cc=quic_neeraju@quicinc.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