Lines Matching refs:KVM_RUN

178 The KVM_RUN ioctl (cf.) communicates with userspace via a shared
180 KVM_RUN documentation for details.
274 4.10 KVM_RUN
551 Defines which signals are blocked during execution of KVM_RUN.  This
554 their traditional behaviour) will cause KVM_RUN to return with -EINTR.
1649 TLB, prior to calling KVM_RUN on the associated vcpu.
1851 prior to calling the KVM_RUN ioctl.
2365 (with the KVM_RUN ioctl), the host kernel will allocate a
2372 re-create the VMRA HPTEs on the next KVM_RUN of any vcpu.)
2555 registers to their initial values.  If this is not called, KVM_RUN will
2569 	  and execute guest code when KVM_RUN is called.
2655 KVM_RUN on any of the VCPUs.  Calling this ioctl twice for any of the
3037 execution by changing fields in kvm_run prior to calling the KVM_RUN
3038 ioctl, and obtain information about the reason KVM_RUN returned by
3045 Request that KVM_RUN return when it becomes possible to inject external
3053 When KVM_RUN has returned successfully (return value 0), this informs
3054 application code why KVM_RUN has returned.  Allowable values for this
3127 KVM_RUN invocation (KVM_EXIT_IO_IN).  Data format is a packed array.
3157 has re-entered the kernel with KVM_RUN.  The kernel side will first finish
3313    KVM_RUN again before shutdown finally occurs).
3316    to schedule the reset to occur in the future and may call KVM_RUN again.
3445 While KVM_RUN is active, the shared region is under control of KVM.  Its
3449 On return from KVM_RUN, the shared region will reflect the current state of
3451 to tell KVM which entries have been changed, prior to calling KVM_RUN again