From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: paulmck@kernel.org
Cc: Joel Fernandes <joel@joelfernandes.org>,
Sandeep Dhavale <dhavale@google.com>,
Frederic Weisbecker <frederic@kernel.org>,
Neeraj Upadhyay <quic_neeraju@quicinc.com>,
Josh Triplett <josh@joshtriplett.org>,
Boqun Feng <boqun.feng@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Zqiang <qiang.zhang1211@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-erofs@lists.ozlabs.org, xiang@kernel.org,
Will Shiu <Will.Shiu@mediatek.com>,
kernel-team@android.com, rcu@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v1] rcu: Fix and improve RCU read lock checks when !CONFIG_DEBUG_LOCK_ALLOC
Date: Thu, 13 Jul 2023 12:51:34 +0800 [thread overview]
Message-ID: <a7078657-823f-6283-bfeb-b5dc2c4c8d09@linux.alibaba.com> (raw)
In-Reply-To: <0d9e7b4d-6477-47a6-b3d2-2c9d9b64903d@paulmck-laptop>
On 2023/7/13 12:27, Paul E. McKenney wrote:
> On Thu, Jul 13, 2023 at 10:02:17AM +0800, Gao Xiang wrote:
>>
>>
... sorry forget some.
>
> One additional question... What is your plan for kernels built with
> CONFIG_PREEMPT_COUNT=n? After all, in such kernels, there is no way
> that I know of for code to determine whether it is in an RCU read-side
> critical section, holding a spinlock, or running with preemption disabled.
I'm not sure if Android (or all targetted) users use or care about
this configuration (CONFIG_PREEMPT_COUNT=n), personally I think
for such configuration we could just fall back to the workqueue
approach all the time.
Anyway, such optimization really comes from real workloads /
experience, users don't live well without such mitigation.
Thanks,
Gao Xiang
>
> Thanx, Paul
prev parent reply other threads:[~2023-07-13 4:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 23:38 [PATCH v1] rcu: Fix and improve RCU read lock checks when !CONFIG_DEBUG_LOCK_ALLOC Sandeep Dhavale
2023-07-12 17:02 ` Joel Fernandes
2023-07-12 21:20 ` Sandeep Dhavale
2023-07-13 0:32 ` Joel Fernandes
2023-07-13 2:02 ` Gao Xiang
2023-07-13 2:10 ` Gao Xiang
2023-07-13 2:16 ` Joel Fernandes
2023-07-13 4:27 ` Paul E. McKenney
2023-07-13 4:41 ` Gao Xiang
2023-07-13 4:52 ` Paul E. McKenney
2023-07-13 4:59 ` Gao Xiang
2023-07-13 14:07 ` Joel Fernandes
2023-07-13 14:34 ` Gao Xiang
2023-07-13 15:33 ` Joel Fernandes
2023-07-13 16:09 ` Alan Huang
2023-07-13 18:14 ` Paul E. McKenney
2023-07-13 19:00 ` Gao Xiang
2023-07-13 22:27 ` Paul E. McKenney
2023-07-13 16:33 ` Paul E. McKenney
2023-07-13 17:05 ` Sandeep Dhavale
2023-07-13 17:35 ` Paul E. McKenney
2023-07-13 18:51 ` Sandeep Dhavale
2023-07-13 22:49 ` Paul E. McKenney
2023-07-13 23:08 ` Sandeep Dhavale
2023-07-13 23:28 ` Paul E. McKenney
2023-07-14 2:16 ` Paul E. McKenney
2023-07-14 3:16 ` Gao Xiang
2023-07-14 13:42 ` Joel Fernandes
2023-07-14 13:51 ` Gao Xiang
2023-07-14 14:56 ` Steven Rostedt
2023-07-14 15:13 ` Paul E. McKenney
2023-07-14 15:35 ` Alan Huang
2023-07-14 15:54 ` Alan Huang
2023-07-14 17:02 ` Paul E. McKenney
2023-07-14 18:40 ` Alan Huang
2023-07-14 18:44 ` Paul E. McKenney
2023-07-14 19:15 ` Sandeep Dhavale
2023-07-14 19:36 ` Paul E. McKenney
2023-07-13 4:51 ` Gao Xiang [this message]
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=a7078657-823f-6283-bfeb-b5dc2c4c8d09@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=Will.Shiu@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=boqun.feng@gmail.com \
--cc=dhavale@google.com \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=matthias.bgg@gmail.com \
--cc=paulmck@kernel.org \
--cc=qiang.zhang1211@gmail.com \
--cc=quic_neeraju@quicinc.com \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=xiang@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