virt/kvm/api.rst

264 The KVM_RUN ioctl (cf.) communicates with userspace via a shared
266 KVM_RUN documentation for details.
375 4.10 KVM_RUN
712 Defines which signals are blocked during execution of KVM_RUN.  This
715 their traditional behaviour) will cause KVM_RUN to return with -EINTR.
1932 TLB, prior to calling KVM_RUN on the associated vcpu.
2112 prior to calling the KVM_RUN ioctl.
2860 (with the KVM_RUN ioctl), the host kernel will allocate a
2870 HPTEs on the next KVM_RUN of any vcpu.
3094 registers to their initial values.  If this is not called, KVM_RUN will
3109 	  and execute guest code when KVM_RUN is called.
3146 	      - KVM_RUN and KVM_GET_REG_LIST are not available;
3260 KVM_RUN on any of the VCPUs.  Calling this ioctl twice for any of the
4564 KVM_RUN, KVM_GET_REG_LIST, KVM_GET_ONE_REG and KVM_SET_ONE_REG, will fail with
4829 execution by changing fields in kvm_run prior to calling the KVM_RUN
4830 ioctl, and obtain information about the reason KVM_RUN returned by
4839 Request that KVM_RUN return when it becomes possible to inject external
4846 This field is polled once when KVM_RUN starts; if non-zero, KVM_RUN
4848 signal is used to "kick" a VCPU out of KVM_RUN, this field can be used
4850 Rather than blocking the signal outside KVM_RUN, userspace can set up
4862 When KVM_RUN has returned successfully (return value 0), this informs
4863 application code why KVM_RUN has returned.  Allowable values for this
4955 KVM_RUN invocation (KVM_EXIT_IO_IN).  Data format is a packed array.
4991       has re-entered the kernel with KVM_RUN.  The kernel side will first finish
5171    KVM_RUN again before shutdown finally occurs).
5174    to schedule the reset to occur in the future and may call KVM_RUN again.
5443 While KVM_RUN is active, the shared region is under control of KVM.  Its
5447 On return from KVM_RUN, the shared region will reflect the current state of
5449 to tell KVM which entries have been changed, prior to calling KVM_RUN again