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
21 The dummy_nmi_callback() function is a "dummy" NMI handler that does
23 the NMI handler to take the default machine-specific action::
28 NMI handler::
45 The do_nmi() function processes each NMI.  It first disables preemption
47 count of NMIs.  It then invokes the NMI handler stored in the nmi_callback
49 default_do_nmi() function to handle a machine-specific NMI.  Finally,
63 Back to the discussion of NMI and RCU::
70 The set_nmi_callback() function registers an NMI handler.  Note that any
73 writes, the rcu_assign_pointer() ensures that the NMI handler sees the
81 This function unregisters an NMI handler, restoring the original
82 dummy_nmi_handler().  However, there may well be an NMI handler
84 up any data structures used by the old NMI handler until execution
97 Since NMI handlers disable preemption, synchronize_rcu() is guaranteed
98 not to return until all ongoing NMI handlers exit.  It is therefore safe
102 invoke nmi_enter() and nmi_exit() on NMI entry and exit, respectively.
110 	initialized some data that is to be used by the new NMI
112 	be needed, because otherwise a CPU that received an NMI
114 	to the new NMI handler, but the old pre-initialized