[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU0-SMTP12157D840AA45B618A39A096620@phx.gbl>
Date: Wed, 8 Jun 2011 19:19:01 -0400
From: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
CC: linux-kernel@...r.kernel.org, mingo@...e.hu, laijs@...fujitsu.com,
dipankar@...ibm.com, akpm@...ux-foundation.org,
josh@...htriplett.org, niv@...ibm.com, tglx@...utronix.de,
peterz@...radead.org, rostedt@...dmis.org, Valdis.Kletnieks@...edu,
dhowells@...hat.com, eric.dumazet@...il.com, darren@...art.com,
patches@...aro.org
Subject: Re: [PATCH tip/core/rcu 10/28] rcu: Fix RCU's NMI documentation
* Paul E. McKenney (paulmck@...ux.vnet.ibm.com) 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@...ux.vnet.ibm.com>
Acked-by: Mathieu Desnoyers <mathieu.desnoyers@...icios.com>
> ---
> 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@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists