diff options
| author | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2015-09-29 09:45:00 -0700 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2015-12-04 12:26:50 -0800 |
| commit | 1de6e56ddc043437d335ee0455a1b34b73510c91 (patch) | |
| tree | dba0371b7d30a406027764a4e782faa0ff0d3d4b /tools/perf/scripts/python/check-perf-trace.py | |
| parent | 06f60de19d3141f07d954c9275fe7ccca8e96b42 (diff) | |
rcu: Clarify role of ->expmaskinitnext
Analogy with the ->qsmaskinitnext field might lead one to believe that
->expmaskinitnext tracks online CPUs. This belief is incorrect: Any CPU
that has ever been online will have its bit set in the ->expmaskinitnext
field. This commit therefore adds a comment to make this clear, at
least to people who read comments.
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Diffstat (limited to 'tools/perf/scripts/python/check-perf-trace.py')
0 files changed, 0 insertions, 0 deletions