Documentation/RCU/NMI-RCU.rst

3 Using RCU to Protect Dynamic NMI Handlers
10 how to do this, drawing loosely from Zwane Mwaikambo's NMI-timer
22 The dummy_nmi_callback() function is a "dummy" NMI handler that does
24 the NMI handler to take the default machine-specific action::
29 NMI handler::
46 The do_nmi() function processes each NMI.  It first disables preemption
48 count of NMIs.  It then invokes the NMI handler stored in the nmi_callback
50 default_do_nmi() function to handle a machine-specific NMI.  Finally,
64 Back to the discussion of NMI and RCU::
71 The set_nmi_callback() function registers an NMI handler.  Note that any
74 writes, the rcu_assign_pointer() ensures that the NMI handler sees the
82 This function unregisters an NMI handler, restoring the original
83 dummy_nmi_handler().  However, there may well be an NMI handler
85 up any data structures used by the old NMI handler until execution
98 Since NMI handlers disable preemption, synchronize_rcu() is guaranteed
99 not to return until all ongoing NMI handlers exit.  It is therefore safe
103 invoke nmi_enter() and nmi_exit() on NMI entry and exit, respectively.
111 	initialized some data that is to be used by the new NMI
113 	be needed, because otherwise a CPU that received an NMI
115 	to the new NMI handler, but the old pre-initialized