Lines Matching refs:IPI
47 order to perform some KVM maintenance. To do so, an IPI is sent, forcing
53 1) Send an IPI. This forces a guest mode exit.
68 as well as to avoid sending unnecessary IPIs (see "IPI Reduction"), and
69 even to ensure IPI acknowledgements are waited upon (see "Waiting for
158 then the caller will wait for each VCPU to acknowledge its IPI before
160 If, for example, the VCPU is sleeping, so no IPI is necessary, then
190 kick will send an IPI to force an exit from guest mode when necessary.
195 enter guest mode. This means that an optimized implementation (see "IPI
196 Reduction") must be certain when it's safe to not send the IPI. One
206 !kvm_request_pending() on its last check and then not receiving an IPI for
220 ...abort guest entry... ...send IPI...
223 As stated above, the IPI is only useful for VCPU threads in guest mode or
231 IPI Reduction
234 As only one IPI is needed to get a VCPU to check for any/all requests,
235 then they may be coalesced. This is easily done by having the first IPI
247 KVM_REQUEST_WAIT flag changes the condition for sending an IPI from
254 As the determination of whether or not to send an IPI depends on the
257 that a non-IPI generating kick will still result in an action by the
261 just about to set its mode to IN_GUEST_MODE, meaning no IPI is sent, then