Searched refs:KVM_RUN (Results 1 – 10 of 10) sorted by relevance
| /linux/tools/testing/selftests/kvm/x86/ |
| H A D | private_mem_kvm_exits_test.c | 36 TEST_ASSERT(errno == EFAULT, KVM_IOCTL_ERROR(KVM_RUN, r)); in run_vcpu_get_exit_reason()
|
| /linux/Documentation/virt/kvm/arm/ |
| H A D | vcpu-features.rst | 33 ``KVM_RUN`` on at least one vCPU in the VM. Userspace can discover what fields
|
| /linux/tools/testing/selftests/kvm/ |
| H A D | guest_print_test.c | 122 TEST_ASSERT(!r, KVM_IOCTL_ERROR(KVM_RUN, r)); in do_vcpu_run()
|
| /linux/Documentation/virt/kvm/ |
| H A D | api.rst | 290 The KVM_RUN ioctl (cf.) communicates with userspace via a shared 292 KVM_RUN documentation for details. 294 Besides the size of the KVM_RUN communication region, other areas of 392 4.10 KVM_RUN 721 - Using KVM_SET_CPUID{,2} after KVM_RUN, i.e. changing the guest vCPU model 754 Defines which signals are blocked during execution of KVM_RUN. This 757 their traditional behaviour) will cause KVM_RUN to return with -EINTR. 1570 event in subsequent calls to KVM_RUN. 1577 calls to KVM_RUN will immediately exit with a KVM_SYSTEM_EVENT_WAKEUP 2156 TLB, prior to calling KVM_RUN on the associated vcpu. [all …]
|
| /linux/tools/testing/selftests/kvm/s390/ |
| H A D | ucontrol_test.c | 422 rc = ioctl(self->vcpu_fd, KVM_RUN, NULL); in uc_run_once()
|
| /linux/include/uapi/linux/ |
| H A D | kvm.h | 1355 #define KVM_RUN _IO(KVMIO, 0x80) macro
|
| /linux/tools/include/uapi/linux/ |
| H A D | kvm.h | 1346 #define KVM_RUN _IO(KVMIO, 0x80) macro
|
| /linux/tools/testing/selftests/kvm/include/ |
| H A D | kvm_util.h | 749 return __vcpu_ioctl(vcpu, KVM_RUN, NULL); in __vcpu_run()
|
| /linux/tools/testing/selftests/kvm/lib/ |
| H A D | kvm_util.c | 1677 TEST_ASSERT(!ret, KVM_IOCTL_ERROR(KVM_RUN, ret)); in vcpu_run()
|
| /linux/virt/kvm/ |
| H A D | kvm_main.c | 4441 case KVM_RUN: { in kvm_vcpu_ioctl()
|