diff options
author | Yury Norov <yury.norov@gmail.com> | 2025-01-28 11:46:35 -0500 |
---|---|---|
committer | Yury Norov <yury.norov@gmail.com> | 2025-02-24 16:37:22 -0500 |
commit | 3268cb2e49cc2a2d142f210efdc82602639d2047 (patch) | |
tree | f1c005fca4ca683ac451b38e1d860fd7cc05ef1b /tools/perf/scripts/python/task-analyzer.py | |
parent | dc5bb9b769c9c3e471609a4e7444ab539c5f3f1f (diff) |
cpumask: re-introduce cpumask_next{,_and}_wrap()
cpumask_next_wrap_old() has two additional parameters, comparing to its
generic counterpart find_next_bit_wrap(). The reason for that is
historical.
Before 4fe49b3b97c262 ("lib/bitmap: introduce for_each_set_bit_wrap()
macro"), cpumask_next_wrap() was used to implement for_each_cpu_wrap()
iterator. Now that the iterator is an alias to generic
for_each_set_bit_wrap(), the additional parameters aren't used and may
confuse readers.
All existing users call cpumask_next_wrap() in a way that makes it
possible to turn it to straight and simple alias to find_next_bit_wrap().
In a couple of places kernel users opencode missing cpumask_next_and_wrap().
Add it as well.
CC: Alexander Gordeev <agordeev@linux.ibm.com>
CC: Bjorn Helgaas <helgaas@kernel.org>
Signed-off-by: Yury Norov <yury.norov@gmail.com>
Diffstat (limited to 'tools/perf/scripts/python/task-analyzer.py')
0 files changed, 0 insertions, 0 deletions