summaryrefslogtreecommitdiff
path: root/tools
diff options
context:
space:
mode:
authorBoqun Feng <boqun.feng@gmail.com>2016-05-25 01:25:33 (GMT)
committerPaul E. McKenney <paulmck@linux.vnet.ibm.com>2016-06-14 23:03:31 (GMT)
commitaf06d4f74a7d2132c805339bfd5ab771b5706f42 (patch)
treef815d4b93b35ee2688b328b95d06603e11231b4e /tools
parent5ef20f872d10c695c30ee036f11c687a23944158 (diff)
downloadlinux-af06d4f74a7d2132c805339bfd5ab771b5706f42.tar.xz
rcuperf: Don't treat gp_exp mis-setting as a WARN
0day found a boot warning triggered in rcu_perf_writer() on !SMP kernel: WARN_ON(rcu_gp_is_normal() && gp_exp); , the root cause of which is trying to measure expedited grace periods(by setting gp_exp to true by default) when all the grace periods are normal(TINY RCU only has normal grace periods). However, such a mis-setting would only result in failing to measure the performance for a specific kind of grace periods, therefore using a WARN_ON to check this is a little overkilling. We could handle this inside rcuperf module via some error messages to tell users about the mis-settings. Therefore this patch removes the WARN_ON in rcu_perf_writer() and handles those checkings in rcu_perf_init() with plain if() code. Moreover, this patch changes the default value of gp_exp to 1) align with rcutorture tests and 2) make the default setting work for all RCU implementations by default. Suggested-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com> Signed-off-by: Boqun Feng <boqun.feng@gmail.com> Fixes: http://lkml.kernel.org/r/57411b10.mFvG0+AgcrMXGtcj%fengguang.wu@intel.com Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions