summaryrefslogtreecommitdiff
path: root/kernel/locking
diff options
context:
space:
mode:
authorZqiang <qiang.zhang1211@gmail.com>2023-11-01 06:35:07 +0300
committerNeeraj Upadhyay (AMD) <neeraj.iitr10@gmail.com>2023-12-13 22:49:02 +0300
commitdee39c0c1e9624f925da4ca0bece46bdc7427257 (patch)
tree71cd78cd0550b84cffdc3157c681c21d241cca38 /kernel/locking
parent23d90b2404050c00c15058710d56bb46e1c5ab36 (diff)
downloadlinux-dee39c0c1e9624f925da4ca0bece46bdc7427257.tar.xz
rcu: Force quiescent states only for ongoing grace period
If an rcutorture test scenario creates an fqs_task kthread, it will periodically invoke rcu_force_quiescent_state() in order to start force-quiescent-state (FQS) operations. However, an FQS operation will be started even if there is no RCU grace period in progress. Although testing FQS operations startup when there is no grace period in progress is necessary, it need not happen all that often. This commit therefore causes rcu_force_quiescent_state() to take an early exit if there is no grace period in progress. Note that there will still be attempts to start an FQS scan in the absence of a grace period because the grace period might end right after the rcu_force_quiescent_state() function's check. In actual testing, this happens about once every ten minutes, which should provide adequate testing. Signed-off-by: Zqiang <qiang.zhang1211@gmail.com> Reviewed-by: Joel Fernandes (Google) <joel@joelfernandes.org> Signed-off-by: Paul E. McKenney <paulmck@kernel.org> Signed-off-by: Neeraj Upadhyay (AMD) <neeraj.iitr10@gmail.com>
Diffstat (limited to 'kernel/locking')
0 files changed, 0 insertions, 0 deletions