Re: [PATCH tip/core/rcu 10/28] rcu: Fix RCU's NMI documentation

[Mathieu Desnoyers]

* Paul E. McKenney (paulmck@xxxxxxxxxxxxxxxxxx) wrote:
> 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@xxxxxxxxxxxxxxxxxx>

Acked-by: Mathieu Desnoyers <mathieu.desnoyers@xxxxxxxxxxxx>

> ---
>  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 a8536cb..84e4f9c 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
> -- 
> 1.7.3.2
> 

-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/