Lines Matching refs:kick

48 The goal of a VCPU kick is to bring a VCPU thread out of guest mode in
51 time of the kick.  Therefore, depending on the mode and state of the VCPU
52 thread, there are two other actions a kick may take.  All three actions
134   to a "kick", but unlike a kick it guarantees the vCPU has actually exited
135   guest mode.  A kick only guarantees the vCPU will exit at some point in the
136   future, e.g. a previous kick may have started the process, but there's no
192 kick will send an IPI to force an exit from guest mode when necessary.
194 kvm_request_pending() check and before it has entered guest mode, as kick
238 sending kick also change the VCPU mode to something !IN_GUEST_MODE.  The
259 that a non-IPI generating kick will still result in an action by the
261 request-accompanying kicks, then the kick may not do anything useful at
262 all.  If, for instance, a request-less kick was made to a VCPU that was
265 whatever it was the kick was meant to initiate.
268 even the request-less VCPU kick is coupled with the same