diff options
| author |   Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2016-02-15 16:52:35 -0800 |
|---|---|---|
| committer | Paul E. McKenney <paulmck@linux.vnet.ibm.com> | 2016-03-31 13:33:21 -0700 |
| commit | 514f1eb5f44520d5255b927ad5aabc00db5bc73d (patch) | |
| tree | 6ca5cc1a495f85e7b6a82d8351906c5a7e964684 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | documentation: Explain why rcu_read_lock() needs no barrier() (diff) | |
| download | linux-dev-514f1eb5f44520d5255b927ad5aabc00db5bc73d.tar.xz linux-dev-514f1eb5f44520d5255b927ad5aabc00db5bc73d.zip | |
documentation: Document illegality of call_rcu() from offline CPUs
There is already a blanket statement about no member of RCU's API
being legal from an offline CPU, but add an explicit note where it
states that it is illegal to invoke call_rcu() from an NMI handler.
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions