Lines Matching full:guest

48 The goal of a VCPU kick is to bring a VCPU thread out of guest mode in
50 a guest mode exit.  However, a VCPU thread may not be in guest mode at the
55 1) Send an IPI.  This forces a guest mode exit.
56 2) Waking a sleeping VCPU.  Sleeping VCPUs are VCPU threads outside guest
60 3) Nothing.  When the VCPU is not in guest mode and the VCPU thread is not
67 guest is running in guest mode or not, as well as some specific
68 outside guest mode states.  The architecture may use ``vcpu->mode`` to
76   The VCPU thread is outside guest mode.
80   The VCPU thread is in guest mode.
89   The VCPU thread is outside guest mode, but it wants the sender of
112   KVM's common MMU notifier may need to flush all of a guest's TLB
131   This "request" ensures the target vCPU has exited guest mode prior to the
135   guest mode.  A kick only guarantees the vCPU will exit at some point in the
137   guarantee the to-be-kicked vCPU has fully exited guest mode.
153   from VCPUs running in guest mode.  That is, sleeping VCPUs do not need
189 executing in guest mode for an arbitrary long time without handling the
191 thread checks kvm_request_pending() before entering guest mode and that a
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
195 IPIs will only trigger guest mode exits for VCPU threads that are in guest
197 enter guest mode.  This means that an optimized implementation (see "IPI
203 - enable interrupts atomically when entering the guest.
222       ...abort guest entry...                 ...send IPI...
225 As stated above, the IPI is only useful for VCPU threads in guest mode or