xiaomi-sm8450/android_kernel_xiaomi_sm8450
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

rcu: Remove rcutorture test version and sequence number

Browse Source 
Back when RCU had a debugfs interface, there was a test version and
sequence number that allowed associating debugfs data with a particular
test run, where the test run started with modprobe and ended with rmmod,
which was how tests were run back on the old ABAT system within IBM.
But rcutorture testing no longer runs on ABAT, and there is no longer an
RCU debugfs interface, so there is no longer any need for test versions
and sequence numbers.

This commit therefore removes the rcutorture_record_test_transition()
and rcutorture_record_progress() functions, and along with them the
rcutorture_testseq and rcutorture_vernum variables that they update.

Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
This commit is contained in:
Paul E. McKenney
2018-05-16 15:30:36 -07:00
parent 028be12b29
commit 6bea2cc5a9
3 changed files with 1 additions and 44 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
kernel/rcu/rcutorture.c
View File

@@ -1016,7 +1016,7 @@ rcu_torture_writer(void *arg)
break;
}
}
rcutorture_record_progress(++rcu_torture_current_version);
rcu_torture_current_version++;
/* Cycle through nesting levels of rcu_expedite_gp() calls. */
if (can_expedite &&
!(torture_random(&rand) & 0xff & (!!expediting - 1))) {
@@ -1613,7 +1613,6 @@ rcu_torture_cleanup(void)
unsigned long gp_seq = 0;
int i;
rcutorture_record_test_transition();
if (torture_cleanup_begin()) {
if (cur_ops->cb_barrier != NULL)
cur_ops->cb_barrier();
@@ -1918,7 +1917,6 @@ rcu_torture_init(void)
goto unwind;
}
}
rcutorture_record_test_transition();
torture_init_end();
return 0;