diff options
| author | Paul E. McKenney | 2011-06-07 17:05:34 -0700 |
|---|---|---|
| committer | Paul E. McKenney | 2011-09-28 21:36:44 -0700 |
| commit | b15a2e7d16cc6f6082d8c6a85349e48588763ffc (patch) | |
| tree | 8296c3bf8599d166e141592d70aa7e41c79fdf60 /Documentation/RCU | |
| parent | bdf2a4364904d6cf2f59b16b0bd86fdc5a2c6152 (diff) | |
rcu: Fix RCU's NMI documentation
It has long been the case that the architecture must call nmi_enter()
and nmi_exit() rather than irq_enter() and irq_exit() in order to
permit RCU read-side critical sections in NMIs. Catch the documentation
up with reality.
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Acked-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Diffstat (limited to 'Documentation/RCU')
| -rw-r--r-- | Documentation/RCU/NMI-RCU.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/RCU/NMI-RCU.txt b/Documentation/RCU/NMI-RCU.txt index bf82851a0e57..687777f83b23 100644 --- a/Documentation/RCU/NMI-RCU.txt +++ b/Documentation/RCU/NMI-RCU.txt @@ -95,7 +95,7 @@ not to return until all ongoing NMI handlers exit. It is therefore safe to free up the handler's data as soon as synchronize_sched() returns. Important note: for this to work, the architecture in question must -invoke irq_enter() and irq_exit() on NMI entry and exit, respectively. +invoke nmi_enter() and nmi_exit() on NMI entry and exit, respectively. Answer to Quick Quiz |