From: Dexuan Cui <decui@microsoft.com>
To: Qian Cai <cai@lca.pw>, Dexuan-Linux Cui <dexuan.linux@gmail.com>
Cc: "paulmck@kernel.org" <paulmck@kernel.org>,
"Joel Fernandes (Google)" <joel@joelfernandes.org>,
Tejun Heo <tj@kernel.org>, Josh Triplett <josh@joshtriplett.org>,
Steven Rostedt <rostedt@goodmis.org>,
"rcu@vger.kernel.org" <rcu@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lili Deng <Lili.Deng@microsoft.com>,
Baihua Lu <Baihua.Lu@microsoft.com>
Subject: RE: "rcu: React to callback overload by aggressively seeking quiescent states" hangs on boot
Date: Sun, 15 Dec 2019 20:19:55 +0000 [thread overview]
Message-ID: <HK0P153MB0148B34EECB0A1A982B25732BF560@HK0P153MB0148.APCP153.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <BCD69C9E-4E61-405F-A514-36096E0F34F4@lca.pw>
> From: Qian Cai <cai@lca.pw>
> Sent: Sunday, December 15, 2019 11:54 AM
> Subject: Re: "rcu: React to callback overload by aggressively seeking
> quiescent states" hangs on boot
>
>
> On Dec 15, 2019, at 2:18 PM, Dexuan-Linux Cui <mailto:dexuan.linux@gmail.com> wrote:
> We're seeing the same hang issue with a recent Linux next-20191213
> kernel. If we revert the same commit 82150cb53dcb ("rcu: React to
> callback overload by aggressively seeking quiescent states”), the
> issue will go away.
>
> Does this patch work for you?
> https://lore.kernel.org/rcu/20191215065242.7155-1-cai@lca.pw/#r
Yes, this can work for me. Thanks!
next prev parent reply other threads:[~2019-12-15 20:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BCD69C9E-4E61-405F-A514-36096E0F34F4@lca.pw>
2019-12-15 20:18 ` "rcu: React to callback overload by aggressively seeking quiescent states" hangs on boot Paul E. McKenney
2019-12-15 20:19 ` Dexuan Cui [this message]
2019-12-13 6:13 Qian Cai
2019-12-13 22:46 ` Paul E. McKenney
2019-12-13 23:11 ` Qian Cai
2019-12-14 6:40 ` Paul E. McKenney
[not found] ` <CAA42JLbBFkpYHXRVvyveYO76DnbkE3gyRW-=qmBGZcJTAiB6Uw@mail.gmail.com>
2019-12-15 19:29 ` Dexuan-Linux Cui
2019-12-15 20:20 ` Paul E. McKenney
2019-12-15 20:40 ` Dexuan Cui
2019-12-15 20:56 ` Paul E. McKenney
2019-12-15 21:02 ` Dexuan Cui
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=HK0P153MB0148B34EECB0A1A982B25732BF560@HK0P153MB0148.APCP153.PROD.OUTLOOK.COM \
--to=decui@microsoft.com \
--cc=Baihua.Lu@microsoft.com \
--cc=Lili.Deng@microsoft.com \
--cc=cai@lca.pw \
--cc=dexuan.linux@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).