Lines Matching refs:KVM_RUN

258 The KVM_RUN ioctl (cf.) communicates with userspace via a shared
260 KVM_RUN documentation for details.
262 Besides the size of the KVM_RUN communication region, other areas of
360 4.10 KVM_RUN
686   - Using KVM_SET_CPUID{,2} after KVM_RUN, i.e. changing the guest vCPU model
719 Defines which signals are blocked during execution of KVM_RUN.  This
722 their traditional behaviour) will cause KVM_RUN to return with -EINTR.
1496 event in subsequent calls to KVM_RUN.
1503      calls to KVM_RUN will immediately exit with a KVM_SYSTEM_EVENT_WAKEUP
2063 TLB, prior to calling KVM_RUN on the associated vcpu.
2243 prior to calling the KVM_RUN ioctl.
3153 (with the KVM_RUN ioctl), the host kernel will allocate a
3163 HPTEs on the next KVM_RUN of any vcpu.
3391 registers to their initial values.  If this is not called, KVM_RUN will
3418 	  and execute guest code when KVM_RUN is called.
3455 	      - KVM_RUN and KVM_GET_REG_LIST are not available;
3569 KVM_RUN on any of the VCPUs.  Calling this ioctl twice for any of the
5022 KVM_RUN, KVM_GET_REG_LIST, KVM_GET_ONE_REG and KVM_SET_ONE_REG, will fail with
6078 execution by changing fields in kvm_run prior to calling the KVM_RUN
6079 ioctl, and obtain information about the reason KVM_RUN returned by
6088 Request that KVM_RUN return when it becomes possible to inject external
6095 This field is polled once when KVM_RUN starts; if non-zero, KVM_RUN
6097 signal is used to "kick" a VCPU out of KVM_RUN, this field can be used
6099 Rather than blocking the signal outside KVM_RUN, userspace can set up
6111 When KVM_RUN has returned successfully (return value 0), this informs
6112 application code why KVM_RUN has returned.  Allowable values for this
6209 KVM_RUN invocation (KVM_EXIT_IO_IN).  Data format is a packed array.
6245       has re-entered the kernel with KVM_RUN.  The kernel side will first finish
6458    KVM_RUN again before shutdown finally occurs).
6461    to schedule the reset to occur in the future and may call KVM_RUN again.
6470    marking the exiting vCPU as runnable, or deny it and call KVM_RUN again.
6683     field before invoking KVM_RUN again.
6844 While KVM_RUN is active, the shared region is under control of KVM.  Its
6848 On return from KVM_RUN, the shared region will reflect the current state of
6850 to tell KVM which entries have been changed, prior to calling KVM_RUN again
8190 The dirty ring can get full.  When it happens, the KVM_RUN of the
8198 needs to kick the vcpu out of KVM_RUN using a signal.  The resulting