Lines Matching refs:IPI

49 order to perform some KVM maintenance.  To do so, an IPI is sent, forcing
55 1) Send an IPI.  This forces a guest mode exit.
70 as well as to avoid sending unnecessary IPIs (see "IPI Reduction"), and
71 even to ensure IPI acknowledgements are waited upon (see "Waiting for
160   then the caller will wait for each VCPU to acknowledge its IPI before
162   If, for example, the VCPU is sleeping, so no IPI is necessary, then
192 kick will send an IPI to force an exit from guest mode when necessary.
197 enter guest mode.  This means that an optimized implementation (see "IPI
198 Reduction") must be certain when it's safe to not send the IPI.  One
208 !kvm_request_pending() on its last check and then not receiving an IPI for
222       ...abort guest entry...                 ...send IPI...
225 As stated above, the IPI is only useful for VCPU threads in guest mode or
233 IPI Reduction
236 As only one IPI is needed to get a VCPU to check for any/all requests,
237 then they may be coalesced.  This is easily done by having the first IPI
249 KVM_REQUEST_WAIT flag changes the condition for sending an IPI from
256 As the determination of whether or not to send an IPI depends on the
259 that a non-IPI generating kick will still result in an action by the
263 just about to set its mode to IN_GUEST_MODE, meaning no IPI is sent, then