diff options
author | Frederic Weisbecker <frederic@kernel.org> | 2022-11-25 16:54:59 +0300 |
---|---|---|
committer | Paul E. McKenney <paulmck@kernel.org> | 2023-01-04 04:52:16 +0300 |
commit | 44757092958bdd749775022f915b7ac974384c2a (patch) | |
tree | f1cf1a9544ade13086d25e0795eca06bda7c2730 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | e4e1e8089c5fd948da12cb9f4adc93821036945f (diff) | |
download | linux-44757092958bdd749775022f915b7ac974384c2a.tar.xz |
rcu-tasks: Remove preemption disablement around srcu_read_[un]lock() calls
Ever since the following commit:
5a41344a3d83 ("srcu: Simplify __srcu_read_unlock() via this_cpu_dec()")
SRCU doesn't rely anymore on preemption to be disabled in order to
modify the per-CPU counter. And even then it used to be done from the API
itself.
Therefore and after checking further, it appears to be safe to remove
the preemption disablement around __srcu_read_[un]lock() in
exit_tasks_rcu_start() and exit_tasks_rcu_finish()
Suggested-by: Boqun Feng <boqun.feng@gmail.com>
Suggested-by: Paul E. McKenney <paulmck@kernel.org>
Suggested-by: Neeraj Upadhyay <quic_neeraju@quicinc.com>
Cc: Lai Jiangshan <jiangshanlai@gmail.com>
Signed-off-by: Frederic Weisbecker <frederic@kernel.org>
Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions