Lines Matching refs:ioctl
11 whole kvm subsystem. In addition a system ioctl is used to create
15 machine, for example memory layout. In addition a VM ioctl is used to
33 can be used to issue system ioctls. A KVM_CREATE_VM ioctl on this
35 ioctls. A KVM_CREATE_VCPU ioctl on a VM fd will create a virtual cpu
66 For each ioctl, the following information is provided along with a
69 Capability: which KVM extension provides this ioctl. Can be 'basic',
74 support this ioctl, there's no capability bit to check its
75 availability: for kernels that don't support the ioctl,
76 the ioctl returns -ENOTTY.
78 Architectures: which instruction set architectures provide this ioctl.
83 Parameters: what parameters are accepted by the ioctl.
93 Type: system ioctl
109 Type: system ioctl
141 This ioctl returns the guest msrs that are supported. The list varies
149 of banks, as set via the KVM_X86_SETUP_MCE ioctl.
154 Capability: basic, KVM_CAP_CHECK_EXTENSION_VM for vm ioctl
156 Type: system ioctl, vm ioctl
167 It is thus encouraged to use the vm ioctl to query for capabilities (available
174 Type: system ioctl
178 The KVM_RUN ioctl (cf.) communicates with userspace via a shared
179 memory region. This ioctl returns the size of that region. See the
187 Type: vm ioctl
191 This ioctl is obsolete and has been removed.
198 Type: vm ioctl
206 the KVM_CHECK_EXTENSION ioctl() at run-time.
208 KVM_CAP_MAX_VCPUS of the KVM_CHECK_EXTENSION ioctl() at run-time.
234 4.8 KVM_GET_DIRTY_LOG (vm ioctl)
238 Type: vm ioctl
253 since the last call to this ioctl. Bit 0 is the first page in the
267 Type: vm ioctl
271 This ioctl is obsolete and has been removed.
278 Type: vcpu ioctl
284 This ioctl is used to run a guest virtual cpu. While there are no
295 Type: vcpu ioctl
325 Type: vcpu ioctl
338 Type: vcpu ioctl
366 Type: vcpu ioctl
378 Type: vcpu ioctl
402 Type: vcpu ioctl
423 ioctl is useful if the in-kernel PIC is not used.
427 Queues an external interrupt to be injected. This ioctl is overleaded
444 interrupt stays pending until a specific ioctl with KVM_INTERRUPT_UNSET
462 Type: vcpu ioctl
473 Type: vcpu ioctl
502 Type: vcpu ioctl
518 Type: vcpu ioctl
523 should use the KVM_SET_CPUID2 ioctl if available.
547 Type: vcpu ioctl
570 Type: vcpu ioctl
596 Type: vcpu ioctl
622 Type: vm ioctl
643 Type: vm ioctl
697 Type: vm ioctl
719 Type: vm ioctl
741 Type: vm ioctl
766 Type: vm ioctl
785 Type: vm ioctl
805 Type: vm ioctl
855 Type: vm ioctl
884 Type: vm ioctl
903 Type: vm ioctl
917 Type: vm ioctl
933 This ioctl allows the user to create or modify a guest physical memory
956 writes to memory within the slot. See KVM_GET_DIRTY_LOG ioctl to know how to
966 It is recommended to use this API instead of the KVM_SET_MEMORY_REGION ioctl.
975 Type: vm ioctl
979 This ioctl defines the physical address of a three-page region in the guest
985 This ioctl is required on Intel-based hosts. This is needed on Intel hardware
995 Type: vcpu ioctl, vm ioctl (with KVM_CAP_ENABLE_CAP_VM)
999 +Not all extensions are enabled by default. Using this ioctl the application
1002 On systems that do not support this ioctl, it always fails. On systems that
1005 To check if a capability can be enabled, the KVM_CHECK_EXTENSION ioctl should
1026 The vcpu ioctl should be used for vcpu-specific capabilities, the vm ioctl
1033 Type: vcpu ioctl
1062 On x86, this ioctl is only useful after KVM_CREATE_IRQCHIP. Without an
1075 Type: vcpu ioctl
1082 On x86, this ioctl is only useful after KVM_CREATE_IRQCHIP. Without an
1095 Type: vm ioctl
1099 This ioctl defines the physical address of a one-page region in the guest
1105 This ioctl is required on Intel-based hosts. This is needed on Intel hardware
1114 Type: vm ioctl
1119 as the vcpu id in KVM_CREATE_VCPU. If this ioctl is not called, the default
1127 Type: vcpu ioctl
1135 This ioctl would copy current vcpu's xsave struct to the userspace.
1142 Type: vcpu ioctl
1150 This ioctl would copy userspace's xsave struct to the kernel.
1157 Type: vcpu ioctl
1174 This ioctl would copy current vcpu's xcrs to the userspace.
1181 Type: vcpu ioctl
1198 This ioctl would set vcpu's xcr to the value userspace specified.
1205 Type: system ioctl
1230 This ioctl returns x86 cpuid features which are supported by both the hardware
1231 and kvm. Userspace can use the information returned by this ioctl to
1270 ioctl(KVM_CHECK_EXTENSION, KVM_CAP_TSC_DEADLINE_TIMER)
1280 Type: vm ioctl
1290 This ioctl fetches PV specific information that need to be passed to the guest
1307 Type: vm ioctl
1343 device assignment. The user requesting this ioctl must have read/write
1347 ENOTTY: kernel does not support this ioctl
1357 Type: vm ioctl
1367 ENOTTY: kernel does not support this ioctl
1376 Type: vm ioctl
1406 ENOTTY: kernel does not support this ioctl
1416 Type: vm ioctl
1431 Type: vm ioctl
1490 Type: vm ioctl
1512 Type: vm ioctl
1527 ENOTTY: kernel does not support this ioctl
1537 Type: vcpu ioctl
1549 Type: vcpu ioctl
1554 KHz. If the host has unstable tsc this ioctl returns -EIO instead as an
1562 Type: vcpu ioctl
1579 Type: vcpu ioctl
1596 Type: vm ioctl
1600 This ioctl attaches or detaches an ioeventfd to a legal pio/mmio address
1639 Type: vcpu ioctl
1672 Type: vm ioctl
1685 physical device command register by calling this ioctl to inform the kernel of
1706 Type: vm ioctl
1727 table has been created using this ioctl(), the kernel will handle it
1742 Type: vm ioctl
1760 passed to the KVM_SET_USER_MEMORY_REGION ioctl to establish it as the
1765 The KVM_CAP_PPC_RMA capability is 1 or 2 if the KVM_ALLOCATE_RMA ioctl
1775 Type: vcpu ioctl
1801 Type: vcpu ioctl
1812 This ioctl maps the memory at "user_addr" with the length "length" to
1821 Type: vcpu ioctl
1832 This ioctl unmaps the memory in the vcpu's address space starting at
1841 Type: vcpu ioctl
1851 prior to calling the KVM_RUN ioctl.
1858 Type: vcpu ioctl
1867 Using this ioctl, a single vcpu register can be set to a specific value
2110 Type: vcpu ioctl
2114 This ioctl allows to receive the value of a single register implemented
2127 Type: vcpu ioctl
2140 itself or when a soft lockup is detected. This ioctl can be called any time
2148 Type: vm ioctl
2170 Type: vm ioctl
2202 Type: vm ioctl
2227 Type: vm ioctl
2241 Type: vm ioctl
2311 Type: vm ioctl
2344 Type: vm ioctl
2351 virtualization. Otherwise the capability doesn't exist and the ioctl
2355 There must be no vcpus running when this ioctl is called; if there
2361 ioctl, it will have been updated with the order of the hash table that
2365 (with the KVM_RUN ioctl), the host kernel will allocate a
2368 If this ioctl is called when a hash table has already been allocated,
2378 Type: vm ioctl, vcpu ioctl
2383 (vm ioctl) or per cpu (vcpu ioctl), depending on the interrupt type.
2413 supported by this ioctl)
2415 Note that the vcpu ioctl is asynchronous to vcpu execution.
2421 Type: vm ioctl
2474 Type: vm ioctl
2505 Type: device ioctl, vm ioctl
2531 Type: device ioctl, vm ioctl
2546 Type: vcpu ioctl
2559 should be created before this ioctl is invoked.
2580 Type: vm ioctl
2589 The ioctl returns struct kvm_vcpu_init instance containing information
2595 The information returned by this ioctl can be used to prepare an instance
2596 of struct kvm_vcpu_init for KVM_ARM_VCPU_INIT ioctl which will result in
2604 Type: vcpu ioctl
2616 This ioctl returns the guest registers that are supported for the
2624 Type: vm ioctl
2653 mapping of the VGIC virtual CPU and distributor interface, the ioctl
2655 KVM_RUN on any of the VCPUs. Calling this ioctl twice for any of the
2666 Type: vm ioctl
2685 Type: vcpu ioctl
2735 Type: system ioctl
2762 This ioctl returns x86 cpuid features which are emulated by
2763 kvm.Userspace can use the information returned by this ioctl to query
2805 Type: vcpu ioctl
2832 ioctl returns a positive error number to indicate the type of exception.
2851 Type: vm ioctl
2856 This ioctl is used to get guest storage key values on the s390
2857 architecture. The ioctl takes parameters via the kvm_s390_skeys struct.
2873 will cause the ioctl to return -EINVAL.
2876 bytes. This buffer will be filled with storage key data by the ioctl.
2882 Type: vm ioctl
2886 This ioctl is used to set guest storage key values on the s390
2887 architecture. The ioctl takes parameters via the kvm_s390_skeys struct.
2896 will cause the ioctl to return -EINVAL.
2903 the ioctl will return -EINVAL.
2909 Type: vcpu ioctl
2958 Note that the vcpu ioctl is asynchronous to vcpu execution.
2964 Type: vcpu ioctl
2971 This ioctl allows userspace to retrieve the complete state of all currently
2993 Type: vcpu ioctl
3002 This ioctl allows userspace to set the complete state of all cpu-local
3016 ioctl aborts.
3026 Type: vcpu ioctl
3038 ioctl, and obtain information about the reason KVM_RUN returned by
3378 Architectures: which instruction set architectures provide this ioctl.
3564 Architectures: which instruction set architectures provide this ioctl.
3591 implementation, the KVM_ENABLE_CAP ioctl will fail with an EINVAL