Lines Matching refs:NMI

1 Using RCU to Protect Dynamic NMI Handlers
7 how to do this, drawing loosely from Zwane Mwaikambo's NMI-timer
19 The dummy_nmi_callback() function is a "dummy" NMI handler that does
21 the NMI handler to take the default machine-specific action.
26 NMI handler.
43 The do_nmi() function processes each NMI.  It first disables preemption
45 count of NMIs.  It then invokes the NMI handler stored in the nmi_callback
47 default_do_nmi() function to handle a machine-specific NMI.  Finally,
60 Back to the discussion of NMI and RCU...
67 The set_nmi_callback() function registers an NMI handler.  Note that any
70 writes, the rcu_assign_pointer() ensures that the NMI handler sees the
78 This function unregisters an NMI handler, restoring the original
79 dummy_nmi_handler().  However, there may well be an NMI handler
81 up any data structures used by the old NMI handler until execution
93 Since NMI handlers disable preemption, synchronize_sched() is guaranteed
94 not to return until all ongoing NMI handlers exit.  It is therefore safe
98 invoke nmi_enter() and nmi_exit() on NMI entry and exit, respectively.
107 		initialized some data that is to be used by the new NMI
109 		be needed, because otherwise a CPU that received an NMI
111 		to the new NMI handler, but the old pre-initialized