Lines Matching refs:KVM_RUN

187 The KVM_RUN ioctl (cf.) communicates with userspace via a shared
189 KVM_RUN documentation for details.
289 4.10 KVM_RUN
574 Defines which signals are blocked during execution of KVM_RUN.  This
577 their traditional behaviour) will cause KVM_RUN to return with -EINTR.
1627 TLB, prior to calling KVM_RUN on the associated vcpu.
1795 prior to calling the KVM_RUN ioctl.
2369 (with the KVM_RUN ioctl), the host kernel will allocate a
2379 HPTEs on the next KVM_RUN of any vcpu.
2566 registers to their initial values.  If this is not called, KVM_RUN will
2580 	  and execute guest code when KVM_RUN is called.
2669 KVM_RUN on any of the VCPUs.  Calling this ioctl twice for any of the
3684 execution by changing fields in kvm_run prior to calling the KVM_RUN
3685 ioctl, and obtain information about the reason KVM_RUN returned by
3692 Request that KVM_RUN return when it becomes possible to inject external
3697 This field is polled once when KVM_RUN starts; if non-zero, KVM_RUN
3699 signal is used to "kick" a VCPU out of KVM_RUN, this field can be used
3701 Rather than blocking the signal outside KVM_RUN, userspace can set up
3711 When KVM_RUN has returned successfully (return value 0), this informs
3712 application code why KVM_RUN has returned.  Allowable values for this
3785 KVM_RUN invocation (KVM_EXIT_IO_IN).  Data format is a packed array.
3815 has re-entered the kernel with KVM_RUN.  The kernel side will first finish
3971    KVM_RUN again before shutdown finally occurs).
3974    to schedule the reset to occur in the future and may call KVM_RUN again.
4131 While KVM_RUN is active, the shared region is under control of KVM.  Its
4135 On return from KVM_RUN, the shared region will reflect the current state of
4137 to tell KVM which entries have been changed, prior to calling KVM_RUN again