Lines Matching +full:cmd +full:- +full:dat +full:- +full:pins
1 .. SPDX-License-Identifier: GPL-2.0
4 The Definitive KVM (Kernel-based Virtual Machine) API Documentation
24 - System ioctls: These query and set global attributes which affect the
28 - VM ioctls: These query and set attributes that affect an entire virtual
35 - vcpu ioctls: These query and set attributes that control the operation
43 - device ioctls: These query and set attributes that control the operation
92 facility that allows backward-compatible extensions to the API to be
133 -----------------------
150 -----------------
189 address used by the VM. The IPA_Bits is encoded in bits[7-0] of the
207 ioctl() at run-time.
219 ----------------------------------------------------------
225 :Returns: 0 on success; -1 on error
263 -----------------------
282 --------------------------
295 the VCPU file descriptor can be mmap-ed, including:
297 - if KVM_CAP_COALESCED_MMIO is available, a page at
302 - if KVM_CAP_DIRTY_LOG_RING is available, a number of pages at
308 -------------------
314 :Returns: vcpu fd on success, -1 on error
320 the KVM_CHECK_EXTENSION ioctl() at run-time.
322 KVM_CAP_MAX_VCPUS of the KVM_CHECK_EXTENSION ioctl() at run-time.
330 KVM_CAP_MAX_VCPU_ID of the KVM_CHECK_EXTENSION ioctl() at run-time.
345 single-threaded guest vcpus, it should make all vcpu ids be a multiple
355 ---------------------
361 :Returns: 0 on success, -1 on error
380 If KVM_CAP_MULTI_ADDRESS_SPACE is available, bits 16-31 of slot field specifies
393 ------------
399 :Returns: 0 on success, -1 on error
420 -----------------
426 :Returns: 0 on success, -1 on error
460 -----------------
466 :Returns: 0 on success, -1 on error
474 ------------------
480 :Returns: 0 on success, -1 on error
497 /* ppc -- see arch/powerpc/include/uapi/asm/kvm.h */
505 ------------------
511 :Returns: 0 on success, -1 on error
518 ------------------
524 :Returns: 0 on success, -1 on error
545 ------------------
570 -EEXIST if an interrupt is already enqueued
571 -EINVAL the irq number is invalid
572 -ENXIO if the PIC is in the kernel
573 -EFAULT if the pointer is invalid
577 ioctl is useful if the in-kernel PIC is not used.
617 RISC-V:
644 -----------------
651 -1 on error
654 Reads the values of MSR-based features that are available for the VM. This
656 The list of msr-based features can be obtained using KVM_GET_MSR_FEATURE_INDEX_LIST
660 Reads model-specific registers from the vcpu. Supported msr indices can
684 -----------------
690 :Returns: number of msrs successfully set (see below), -1 on error
692 Writes model-specific registers to the vcpu. See KVM_GET_MSRS for the
706 ------------------
712 :Returns: 0 on success, -1 on error
718 - If this IOCTL fails, KVM gives no guarantees that previous valid CPUID
721 - Using KVM_SET_CPUID{,2} after KVM_RUN, i.e. changing the guest vCPU model
723 - Using heterogeneous CPUID configurations, modulo APIC IDs, topology, etc...
746 ------------------------
752 :Returns: 0 on success, -1 on error
757 their traditional behaviour) will cause KVM_RUN to return with -EINTR.
772 ----------------
778 :Returns: 0 on success, -1 on error
810 ----------------
816 :Returns: 0 on success, -1 on error
848 -----------------------
854 :Returns: 0 on success, -1 on error
858 future vcpus to have a local APIC. IRQ routing for GSIs 0-15 is set to both
859 PIC and IOAPIC; GSI 16-23 only go to the IOAPIC.
870 -----------------
876 :Returns: 0 on success, -1 on error
880 been previously created with KVM_CREATE_IRQCHIP. Note that edge-triggered
883 On real hardware, interrupt pins can be active-low or active-high. This
888 (active-low/active-high) for level-triggered interrupts, and KVM used
890 active-low interrupts, the above convention is now valid on x86 too.
892 should not present interrupts to the guest as active-low unless this
893 capability is present (or unless it is not using the in-kernel irqchip,
898 in-kernel irqchip (GIC), and for in-kernel irqchip can tell the GIC to
907 - KVM_ARM_IRQ_TYPE_CPU:
908 out-of-kernel GIC: irq_id 0 is IRQ, irq_id 1 is FIQ
909 - KVM_ARM_IRQ_TYPE_SPI:
910 in-kernel GIC: SPI, irq_id between 32 and 1019 (incl.)
912 - KVM_ARM_IRQ_TYPE_PPI:
913 in-kernel GIC: PPI, irq_id between 16 and 31 (incl.)
924 injection of interrupts for the in-kernel irqchip. KVM_IRQ_LINE can always
939 --------------------
945 :Returns: 0 on success, -1 on error
964 --------------------
970 :Returns: 0 on success, -1 on error
989 -----------------------
995 :Returns: 0 on success, -1 on error
1000 page of a blob (32- or 64-bit, depending on the vcpu mode) to guest
1039 ------------------
1045 :Returns: 0 on success, -1 on error
1089 ------------------
1095 :Returns: 0 on success, -1 on error
1124 ------------------------
1131 :Returns: 0 on success, -1 on error
1176 - KVM_VCPUEVENT_VALID_SHADOW may be set to signal that
1179 - KVM_VCPUEVENT_VALID_SMM may be set to signal that smi contains a
1182 - KVM_VCPUEVENT_VALID_PAYLOAD may be set to signal that the
1187 - KVM_VCPUEVENT_VALID_TRIPLE_FAULT may be set to signal that the
1206 guest-visible registers. It is not possible to 'cancel' an SError that has been
1209 A device being emulated in user-space may also wish to generate an SError. To do
1210 this the events structure can be populated by user-space. The current state
1219 always have a non-zero value when read, and the agent making an SError pending
1221 the system supports KVM_CAP_ARM_INJECT_SERROR_ESR, but user-space sets the events
1225 -EINVAL. Setting anything other than the lower 24bits of exception.serror_esr
1226 will return -EINVAL.
1247 ------------------------
1254 :Returns: 0 on success, -1 on error
1267 suppress overwriting the current in-kernel state. The bits are:
1272 KVM_VCPUEVENT_VALID_SMM transfer the smi sub-struct.
1314 ----------------------
1320 :Returns: 0 on success, -1 on error
1336 ----------------------
1342 :Returns: 0 on success, -1 on error
1351 -------------------------------
1357 :Returns: 0 on success, -1 on error
1374 memory slot. Bits 0-15 of "slot" specify the slot id and this value
1379 If KVM_CAP_MULTI_ADDRESS_SPACE is available, bits 16-31 of "slot"
1406 to make a new slot read-only. In this case, writes to this memory will be
1415 Read only region isn't supported. Only as-id 0 is supported.
1417 Note: On arm64, a write generated by the page-table walker (to update
1421 page-table walker, making it impossible to emulate the access.
1422 Instead, an abort (data abort if the cause of the page-table update
1429 Returns -EINVAL or -EEXIST if the VM has the KVM_VM_S390_UCONTROL flag set.
1430 Returns -EINVAL if called on a protected VM.
1433 ---------------------
1439 :Returns: 0 on success, -1 on error
1441 This ioctl defines the physical address of a three-page region in the guest
1447 This ioctl is required on Intel-based hosts. This is needed on Intel hardware
1455 -------------------
1461 :Returns: 0 on success; -1 on error
1467 :Returns: 0 on success; -1 on error
1506 The vcpu ioctl should be used for vcpu-specific capabilities, the vm ioctl
1507 for vm-wide capabilities.
1510 ---------------------
1516 :Returns: 0 on success; -1 on error
1551 in-kernel irqchip, the multiprocessing state must be maintained by userspace on
1591 ---------------------
1597 :Returns: 0 on success; -1 on error
1603 in-kernel irqchip, the multiprocessing state must be maintained by userspace on
1616 ------------------------------
1622 :Returns: 0 on success, -1 on error
1624 This ioctl defines the physical address of a one-page region in the guest
1633 This ioctl is required on Intel-based hosts. This is needed on Intel hardware
1640 ------------------------
1646 :Returns: 0 on success, -1 on error
1655 ------------------
1661 :Returns: 0 on success, -1 on error
1675 ------------------
1681 :Returns: 0 on success, -1 on error
1703 -----------------
1709 :Returns: 0 on success, -1 on error
1730 -----------------
1736 :Returns: 0 on success, -1 on error
1757 ----------------------------
1763 :Returns: 0 on success, -1 on error
1796 Dynamically-enabled feature bits need to be requested with
1806 with the 'nent' field indicating the number of entries in the variable-size
1836 may be returned as true, but they depend on KVM_CREATE_IRQCHIP for in-kernel
1849 -----------------------
1879 ------------------------
1885 :Returns: 0 on success, -1 on error
1891 - GSI routing does not apply to KVM_IRQ_LINE but only to KVM_IRQFD.
1928 error -EINVAL.
1932 - KVM_MSI_VALID_DEVID: used along with KVM_IRQ_ROUTING_MSI routing entry
1933 type, specifies that the devid field contains a valid value. The per-VM
1937 - zero otherwise
1962 address_hi bits 31-8 provide bits 31-8 of the destination id. Bits 7-0 of
1996 --------------------
2002 :Returns: 0 on success, -1 on error
2019 --------------------
2025 :Returns: virtual tsc-khz on success, negative value on error
2028 KHz. If the host has unstable tsc this ioctl returns -EIO instead as an
2033 ------------------
2039 :Returns: 0 on success, -1 on error
2054 the APIC_ID register (bytes 32-35). xAPIC only allows an 8-bit APIC ID
2055 which is stored in bits 31-24 of the APIC register, or equivalently in
2064 ------------------
2070 :Returns: 0 on success, -1 on error
2082 The format of the APIC ID register (bytes 32-35 of struct kvm_lapic_state's
2088 ------------------
2111 For the special case of virtio-ccw devices on s390, the ioevent is matched
2125 For virtio-ccw devices, addr contains the subchannel id and datamatch the
2134 ------------------
2140 :Returns: 0 on success, -1 on error
2160 The array is little-endian: the bit 0 is the least significant bit of the
2170 -------------------------
2179 is an IOMMU for PAPR-style virtual I/O. It is used to translate
2193 which this TCE table will translate - the table will contain one 64
2203 the entries written by kernel-handled H_PUT_TCE calls, and also lets
2209 ------------
2215 :Returns: 0 on success, -1 on error
2225 - pause the vcpu
2226 - read the local APIC's state (KVM_GET_LAPIC)
2227 - check whether changing LINT1 will queue an NMI (see the LVT entry for LINT1)
2228 - if so, issue KVM_NMI
2229 - resume the vcpu
2236 ----------------------
2258 ------------------------
2280 ------------------------
2298 --------------------
2541 ARM 32-bit CP15 registers have the following id bit patterns::
2545 ARM 64-bit CP15 registers have the following id bit patterns::
2553 ARM 32-bit VFP control registers have the following id bit patterns::
2557 ARM 64-bit FP registers have the following id bit patterns::
2561 ARM firmware pseudo-registers have the following bit pattern::
2569 arm64 core/FP-SIMD registers have the following id bit patterns. Note
2603 .. [1] These encodings are not accepted for SVE-enabled vcpus. See
2628 arm64 firmware pseudo-registers have the following bit pattern::
2637 0x6060 0000 0015 ffff KVM_REG_ARM64_SVE_VLS pseudo-register
2640 ENOENT. max_vq is the vcpu's maximum supported vector length in 128-bit
2651 KVM_REG_ARM64_SVE_VLS is a pseudo-register that allows the set of vector
2661 ((vector_lengths[(vq - KVM_ARM64_SVE_VQ_MIN) / 64] >>
2662 ((vq - KVM_ARM64_SVE_VQ_MIN) % 64)) & 1))
2684 is hardware-dependent and may not be available. Attempting to configure
2691 arm64 bitmap feature firmware pseudo-registers have the following bit pattern::
2705 a -EBUSY to userspace.
2718 patterns depending on whether they're 32-bit or 64-bit registers::
2720 0x7020 0000 0001 00 <reg:5> <sel:3> (32-bit)
2721 0x7030 0000 0001 00 <reg:5> <sel:3> (64-bit)
2746 0x7020 0000 0003 00 <0:3> <reg:5> (32-bit FPU registers)
2747 0x7030 0000 0003 00 <0:3> <reg:5> (64-bit FPU registers)
2748 0x7040 0000 0003 00 <0:3> <reg:5> (128-bit MSA vector registers)
2760 RISC-V registers are mapped using the lower 32 bits. The upper 8 bits of
2763 RISC-V config registers are meant for configuring a Guest VCPU and it has
2769 Following are the RISC-V config registers:
2781 RISC-V core registers represent the general execution state of a Guest VCPU
2787 Following are the RISC-V core registers:
2824 0x80x0 0000 0200 0020 mode Privilege mode (1 = S-mode or 0 = U-mode)
2827 RISC-V csr registers represent the supervisor mode control/status registers
2833 Following are the RISC-V csr registers:
2849 RISC-V timer registers represent the timer state of a Guest VCPU and it has
2854 Following are the RISC-V timer registers:
2859 0x8030 0000 0400 0000 frequency Time base frequency (read-only)
2865 RISC-V F-extension registers represent the single precision floating point
2870 Following are the RISC-V F-extension registers:
2881 RISC-V D-extension registers represent the double precision floating point
2885 0x8030 0000 06 <index into the __riscv_d_ext_state struct:24> (non-fcsr)
2887 Following are the RISC-V D-extension registers:
2904 0x9030 0000 0001 00 <reg:5> <sel:3> (64-bit)
2913 --------------------
2943 ----------------------
2949 :Returns: 0 on success, -1 on error
2960 load-link/store-conditional, or equivalent must be used. There are two cases
2967 -------------------
2973 :Returns: >0 on delivery, 0 if guest blocked the MSI, and -1 on error
2975 Directly inject a MSI message. Only valid with in-kernel irqchip that handles
2990 KVM_MSI_VALID_DEVID: devid contains a valid value. The per-VM
3001 address_hi bits 31-8 provide bits 31-8 of the destination id. Bits 7-0 of
3006 --------------------
3012 :Returns: 0 on success, -1 on error
3014 Creates an in-kernel device model for the i8254 PIT. This call is only valid
3015 after enabling in-kernel irqchip support via KVM_CREATE_IRQCHIP. The following
3027 PIT timer interrupts may use a per-VM kernel thread for injection. If it
3030 kvm-pit/<owner-process-pid>
3039 -----------------
3045 :Returns: 0 on success, -1 on error
3047 Retrieves the state of the in-kernel PIT model. Only valid after
3067 -----------------
3073 :Returns: 0 on success, -1 on error
3075 Sets the state of the in-kernel PIT model. Only valid after KVM_CREATE_PIT2.
3082 --------------------------
3088 :Returns: 0 on success, -1 on error
3093 device-tree properties for the guest operating system.
3107 - KVM_PPC_PAGE_SIZES_REAL:
3112 - KVM_PPC_1T_SEGMENTS
3116 - KVM_PPC_NO_HASH
3157 --------------
3163 :Returns: 0 on success, -1 on error
3173 With KVM_CAP_IRQFD_RESAMPLE, KVM_IRQFD supports a de-assert and notify
3174 mechanism allowing emulation of level-triggered, irqfd-based
3179 as from an EOI, the gsi is de-asserted and the user is notified via
3180 kvm_irqfd.resamplefd. It is the user's responsibility to re-queue
3188 - in case no routing entry is associated to this gsi, injection fails
3189 - in case the gsi is associated to an irqchip routing entry,
3191 - in case the gsi is associated to an MSI routing entry, the MSI
3193 to GICv3 ITS in-kernel emulation).
3196 --------------------------
3202 :Returns: 0 on success, -1 on error
3214 The parameter is a pointer to a 32-bit unsigned integer variable
3221 default-sized hash table (16 MB).
3229 real-mode area (VRMA) facility, the kernel will re-create the VMRA
3233 -----------------------
3239 :Returns: 0 on success, -1 on error
3255 - sigp stop; optional flags in parm
3257 - program check; code in parm
3259 - sigp set prefix; prefix address in parm
3261 - restart
3263 - clock comparator interrupt
3265 - CPU timer interrupt
3267 - virtio external interrupt; external interrupt
3270 - sclp external interrupt; sclp parameter in parm
3272 - sigp emergency; source cpu in parm
3274 - sigp external call; source cpu in parm
3276 - compound value to indicate an
3277 I/O interrupt (ai - adapter interrupt; cssid,ssid,schid - subchannel);
3281 - machine check interrupt; cr 14 bits in parm, machine check interrupt
3288 ------------------------
3294 :Returns: file descriptor number (>= 0) on success, -1 on error
3343 ----------------------
3349 :Returns: 0 on success, -1 on error
3382 --------------------------------------------
3390 :Returns: 0 on success, -1 on error
3398 (e.g. read-only attribute, or attribute that only makes
3405 semantics are device-specific. See individual device documentation in
3413 __u32 group; /* device-defined */
3414 __u64 attr; /* group-defined */
3419 ------------------------
3426 :Returns: 0 on success, -1 on error
3443 ----------------------
3449 :Returns: 0 on success; -1 on error
3464 - Processor state:
3469 - General Purpose registers, including PC and SP: set to 0
3470 - FPSIMD/NEON registers: set to 0
3471 - SVE registers: set to 0
3472 - System registers: Reset to their architecturally defined
3486 - KVM_ARM_VCPU_POWER_OFF: Starts the CPU in a power-off state.
3489 - KVM_ARM_VCPU_EL1_32BIT: Starts the CPU in a 32bit mode.
3491 - KVM_ARM_VCPU_PSCI_0_2: Emulate PSCI v0.2 (or a future revision
3494 - KVM_ARM_VCPU_PMU_V3: Emulate PMUv3 for the CPU.
3497 - KVM_ARM_VCPU_PTRAUTH_ADDRESS: Enables Address Pointer authentication
3505 - KVM_ARM_VCPU_PTRAUTH_GENERIC: Enables Generic Pointer authentication
3513 - KVM_ARM_VCPU_SVE: Enables SVE for the CPU (arm64 only).
3519 - KVM_REG_ARM64_SVE_VLS may be read using KVM_GET_ONE_REG: the
3520 initial value of this pseudo-register indicates the best set of
3525 - KVM_RUN and KVM_GET_REG_LIST are not available;
3527 - KVM_GET_ONE_REG and KVM_SET_ONE_REG cannot be used to access
3532 - KVM_REG_ARM64_SVE_VLS may optionally be written using
3538 - the KVM_REG_ARM64_SVE_VLS pseudo-register is immutable, and can
3541 - KVM_ARM_VCPU_HAS_EL2: Enable Nested Virtualisation support,
3547 - KVM_ARM_VCPU_HAS_EL2_E2H0: Restrict Nested Virtualisation
3548 support to HCR_EL2.E2H being RES0 (non-VHE).
3553 -----------------------------
3559 :Returns: 0 on success; -1 on error
3572 kvm_vcpu_init->features bitmap returned will have feature bits set if
3582 ---------------------
3588 :Returns: 0 on success; -1 on error
3610 - KVM_REG_S390_TODPR
3612 - KVM_REG_S390_EPOCHDIFF
3614 - KVM_REG_S390_CPU_TIMER
3616 - KVM_REG_S390_CLOCK_COMP
3618 - KVM_REG_S390_PFTOKEN
3620 - KVM_REG_S390_PFCOMPARE
3622 - KVM_REG_S390_PFSELECT
3624 - KVM_REG_S390_PP
3626 - KVM_REG_S390_GBEA
3630 -----------------------------------------
3636 :Returns: 0 on success, -1 on error
3666 arm64 currently only require this when using the in-kernel GIC
3672 base addresses will return -EEXIST.
3679 ------------------------------
3685 :Returns: 0 on success, -1 on error
3690 of a service that has a kernel-side implementation. If the token
3691 value is non-zero, it will be associated with that service, and
3699 ------------------------
3705 :Returns: 0 on success; -1 on error
3720 - KVM_GUESTDBG_ENABLE: guest debugging is enabled
3721 - KVM_GUESTDBG_SINGLESTEP: the next run should single-step
3726 - KVM_GUESTDBG_USE_SW_BP: using software breakpoints [x86, arm64]
3727 - KVM_GUESTDBG_USE_HW_BP: using hardware breakpoints [x86, s390]
3728 - KVM_GUESTDBG_USE_HW: using hardware debug events [arm64]
3729 - KVM_GUESTDBG_INJECT_DB: inject DB type exception [x86]
3730 - KVM_GUESTDBG_INJECT_BP: inject BP type exception [x86]
3731 - KVM_GUESTDBG_EXIT_PENDING: trigger an immediate guest exit [s390]
3732 - KVM_GUESTDBG_BLOCKIRQ: avoid injecting interrupts/NMI/SMI [x86]
3750 the single-step debug event (KVM_GUESTDBG_SINGLESTEP) is supported.
3760 ---------------------------
3766 :Returns: 0 on success, -1 on error
3801 the variable-size array 'entries'. If the number of entries is too low
3835 --------------------
3842 < 0 on generic error (e.g. -EFAULT or -ENOMEM),
3900 Logical accesses are permitted for non-protected guests only.
3918 translation-exception identifier (TEID) indicates suppression.
3941 Absolute accesses are permitted for non-protected guests only.
3980 -----------------------
4006 will cause the ioctl to return -EINVAL.
4012 -----------------------
4030 will cause the ioctl to return -EINVAL.
4037 the ioctl will return -EINVAL.
4040 -----------------
4046 :Returns: 0 on success, -1 on error
4087 - KVM_S390_SIGP_STOP - sigp stop; parameter in .stop
4088 - KVM_S390_PROGRAM_INT - program check; parameters in .pgm
4089 - KVM_S390_SIGP_SET_PREFIX - sigp set prefix; parameters in .prefix
4090 - KVM_S390_RESTART - restart; no parameters
4091 - KVM_S390_INT_CLOCK_COMP - clock comparator interrupt; no parameters
4092 - KVM_S390_INT_CPU_TIMER - CPU timer interrupt; no parameters
4093 - KVM_S390_INT_EMERGENCY - sigp emergency; parameters in .emerg
4094 - KVM_S390_INT_EXTERNAL_CALL - sigp external call; parameters in .extcall
4095 - KVM_S390_MCHK - machine check interrupt; parameters in .mchk
4100 ---------------------------
4107 -EINVAL if buffer size is 0,
4108 -ENOBUFS if buffer size is too small to fit all pending interrupts,
4109 -EFAULT if the buffer address was invalid
4127 the kernel never checked for flags == 0 and QEMU never pre-zeroed flags and
4131 If -ENOBUFS is returned the buffer provided was too small and userspace
4135 ---------------------------
4142 -EFAULT if the buffer address was invalid,
4143 -EINVAL for an invalid buffer length (see below),
4144 -EBUSY if there were already interrupts pending,
4148 This ioctl allows userspace to set the complete state of all cpu-local
4170 which is the maximum number of possibly pending cpu-local interrupts.
4173 ------------
4179 :Returns: 0 on success, -1 on error
4184 ----------------------------
4273 part of VM-Enter/VM-Exit emulation.
4276 of VM-Enter/VM-Exit emulation. If an MSR access is denied on VM-Enter, KVM
4277 synthesizes a consistency check VM-Exit(EXIT_REASON_MSR_LOAD_FAIL). If an
4278 MSR access is denied on VM-Exit, KVM synthesizes a VM-Abort. In short, KVM
4280 the VM-Enter/VM-Exit MSR list. It is platform owner's responsibility to
4297 ----------------------------
4330 -------------------------
4337 -EFAULT if struct kvm_reinject_control cannot be read,
4338 -ENXIO if KVM_CREATE_PIT or KVM_CREATE_PIT2 didn't succeed earlier.
4357 ------------------------------
4364 -EFAULT if struct kvm_ppc_mmuv3_cfg cannot be read,
4365 -EINVAL if the configuration is invalid
4391 ---------------------------
4398 -EFAULT if struct kvm_ppc_rmmu_info cannot be written,
4399 -EINVAL if no useful information can be returned
4428 --------------------------------
4437 -EFAULT if struct kvm_reinject_control cannot be read,
4438 -EINVAL if the supplied shift or flags are invalid,
4439 -ENOMEM if unable to allocate the new HPT,
4472 returns 0 (i.e. cancels any in-progress preparation).
4475 flags will result in an -EINVAL.
4482 -------------------------------
4489 -EFAULT if struct kvm_reinject_control cannot be read,
4490 -EINVAL if the supplied shift or flags are invalid,
4491 -ENXIO is there is no pending HPT, or the pending HPT doesn't
4493 -EBUSY if the pending HPT is not fully prepared,
4494 -ENOSPC if there was a hash collision when moving existing
4496 -EIO on other error conditions
4513 KVM_PPC_RESIZE_HPT_COMMIT will return an error (usually -ENXIO or
4514 -EBUSY, though others may be possible if the preparation was started,
4527 -----------------------------------
4533 :Returns: 0 on success, -1 on error
4540 -----------------------
4547 -EFAULT if u64 mcg_cap cannot be read,
4548 -EINVAL if the requested number of banks is invalid,
4549 -EINVAL if requested MCE capability is not supported.
4554 supported number of error-reporting banks can be retrieved when
4559 ---------------------
4566 -EFAULT if struct kvm_x86_mce cannot be read,
4567 -EINVAL if the bank number is invalid,
4568 -EINVAL if VAL bit is not set in status field.
4593 ----------------------------
4616 - During live migration to save the CMMA values. Live migration needs
4618 - To non-destructively peek at the CMMA values, with the flag
4649 KVM_S390_SKEYS_MAX. KVM_S390_SKEYS_MAX is re-used for consistency with
4694 ----------------------------
4733 This ioctl can fail with -ENOMEM if not enough memory can be allocated to
4734 complete the task, with -ENXIO if CMMA is not enabled, with -EINVAL if
4736 if the flags field was not 0, with -EFAULT if the userspace address is
4742 --------------------------
4749 -EFAULT if struct kvm_ppc_cpu_char cannot be written
4754 CVE-2017-5715, CVE-2017-5753 and CVE-2017-5754). The information is
4771 with preventing inadvertent information disclosure - specifically,
4772 whether there is an instruction to flash-invalidate the L1 data cache
4789 ---------------------------
4795 :Returns: 0 on success; -1 on error
4798 for issuing platform-specific memory encryption commands to manage those
4804 Documentation/virt/kvm/x86/amd-memory-encryption.rst and
4805 Documentation/virt/kvm/x86/intel-tdx.rst.
4808 -----------------------------------
4814 :Returns: 0 on success; -1 on error
4819 It is used in the SEV-enabled guest. When encryption is enabled, a guest
4832 -------------------------------------
4838 :Returns: 0 on success; -1 on error
4844 ------------------------
4852 the specified Hyper-V connection id through the SIGNAL_EVENT hypercall, without
4853 causing a user exit. SIGNAL_EVENT hypercall with non-zero event flag number
4854 (bits 24-31) still triggers a KVM_EXIT_HYPERV_HCALL user exit.
4874 -EINVAL if conn_id or flags is outside the allowed range,
4875 -ENOENT on deassign if the conn_id isn't registered,
4876 -EEXIST on assign if the conn_id is already registered
4879 --------------------------
4885 :Returns: 0 on success, -1 on error
4953 --------------------------
4959 :Returns: 0 on success, -1 on error
4965 -------------------------------------
4994 -------------------------
5000 :Returns: 0 on success, -1 on error
5022 in KVM's dirty bitmap, and dirty tracking is re-enabled for that page
5023 (for example via write-protection, or by clearing the dirty bit in
5026 If KVM_CAP_MULTI_ADDRESS_SPACE is available, bits 16-31 of slot field specifies
5036 --------------------------------
5042 :Returns: 0 on success, -1 on error
5063 This ioctl returns x86 cpuid features leaves related to Hyper-V emulation in
5065 cpuid information presented to guests consuming Hyper-V enlightenments (e.g.
5066 Windows or Hyper-V guests).
5068 CPUID feature leaves returned by this ioctl are defined by Hyper-V Top Level
5075 - HYPERV_CPUID_VENDOR_AND_MAX_FUNCTIONS
5076 - HYPERV_CPUID_INTERFACE
5077 - HYPERV_CPUID_VERSION
5078 - HYPERV_CPUID_FEATURES
5079 - HYPERV_CPUID_ENLIGHTMENT_INFO
5080 - HYPERV_CPUID_IMPLEMENT_LIMITS
5081 - HYPERV_CPUID_NESTED_FEATURES
5082 - HYPERV_CPUID_SYNDBG_VENDOR_AND_MAX_FUNCTIONS
5083 - HYPERV_CPUID_SYNDBG_INTERFACE
5084 - HYPERV_CPUID_SYNDBG_PLATFORM_CAPABILITIES
5087 with the 'nent' field indicating the number of entries in the variable-size
5088 array 'entries'. If the number of entries is too low to describe all Hyper-V
5090 to the number of Hyper-V feature leaves, the 'nent' field is adjusted to the
5100 - HYPERV_CPUID_NESTED_FEATURES leaf and HV_X64_ENLIGHTENED_VMCS_RECOMMENDED
5103 - HV_STIMER_DIRECT_MODE_AVAILABLE bit is only exposed with in-kernel LAPIC.
5107 ---------------------------
5112 :Returns: 0 on success, -1 on error
5138 that should be performed and how to do it are feature-dependent.
5142 -EPERM unless the feature has already been finalized by means of a
5149 ------------------------------
5155 :Returns: 0 on success, -1 on error
5208 ---- -----------
5237 When setting a new pmu event filter, -EINVAL will be returned if any of the
5249 Specifically, KVM follows the following pseudo-code when determining whether to
5250 allow the guest FixCtr[i] to count its pre-defined fixed event::
5265 ---------------------
5289 ---------------------------
5301 ----------------------------
5314 --------------------------
5328 -------------------------
5339 __u32 cmd; /* Command to be executed */
5355 **cmd values:**
5373 All registered VCPUs are converted back to non-protected ones. If a
5474 not succeed all other subcommands will fail with -EINVAL. This
5475 subcommand will return -EINVAL if a dump process has not yet been
5506 resume execution immediately as non-protected. There can be at most
5531 --------------------------
5577 Sets the ABI mode of the VM to 32-bit or 64-bit (long mode). This
5611 re-mapped in guest physical address space.
5617 This is the HVM-wide vector injected directly by the hypervisor
5639 the 32-bit version code returned to the guest when it invokes the
5654 --------------------------
5667 ---------------------------
5752 other four times. The state field must be set to -1, or to a valid
5760 vCPU ID of the given vCPU, to allow timer-related VCPU operations to
5773 per-vCPU local APIC upcall vector, configured by a Xen guest with
5775 used by Windows guests, and is distinct from the HVM-wide upcall
5781 ---------------------------
5796 ---------------------------
5802 :Returns: number of bytes copied, < 0 on error (-EINVAL for incorrect
5803 arguments, -EFAULT if memory cannot be accessed).
5817 ``length`` must not be bigger than 2^31 - PAGE_SIZE bytes. The ``addr``
5834 --------------------
5840 :Returns: 0 on success, -1 on error
5867 --------------------
5873 :Returns: 0 on success, -1 on error
5880 ----------------------
5899 +-------------+
5901 +-------------+
5903 +-------------+
5905 +-------------+
5907 +-------------+
5997 Bits 0-3 of ``flags`` encode the type:
6019 is [``hist_param``*(N-1), ``hist_param``*N), while the range of the last
6020 bucket is [``hist_param``*(``size``-1), +INF). (+INF means positive infinity
6025 [0, 1), while the range of the last bucket is [pow(2, ``size``-2), +INF).
6027 [pow(2, N-2), pow(2, N-1)).
6029 Bits 4-7 of ``flags`` encode the unit:
6052 Bits 8-11 of ``flags``, together with ``exponent``, encode the scale of the
6057 CPU clock cycles. For example, an exponent of -9 can be used with
6073 bucket in the unit expressed by bits 4-11 of ``flags`` together with ``exponent``.
6079 The Stats Data block contains an array of 64-bit values in the same order
6083 --------------------
6089 :Returns: 0 on success, -1 on error
6110 -----------------------------
6130 -----------------------------
6139 for vcpus. It re-uses the kvm_s390_pv_dmp struct and hence also shares
6155 ----------------------
6163 Used to manage hardware-assisted virtualization features for zPCI devices.
6202 --------------------------------
6210 This capability indicates that userspace is able to apply a single VM-wide
6231 (-EINVAL) being returned. This ioctl can also return -EBUSY if any vcpu
6242 ------------------------------------
6281 op0==3, op1=={0, 1, 3}, CRn==0, CRm=={0-7}, op2=={0-7}.
6290 ---------------------------------
6296 :Returns: 0 on success, -1 on error
6326 on-demand.
6337 Returns -EINVAL if the VM has the KVM_VM_S390_UCONTROL flag set.
6338 Returns -EINVAL if called on a protected VM.
6341 -------------------------------
6377 ----------------------------
6420 ---------------------------
6452 KVM_PRE_FAULT_MEMORY populates KVM's stage-2 page tables used to map memory
6454 stage-2 read page fault, e.g. faults in memory as needed, but doesn't break
6455 CoW. However, KVM does not mark any newly created stage-2 PTE as Accessed.
6504 This field is polled once when KVM_RUN starts; if non-zero, KVM_RUN
6505 exits immediately, returning -EINTR. In the common scenario where a
6509 a signal handler that sets run->immediate_exit to a non-zero value.
6535 The value of the current interrupt flag. Only valid if in-kernel
6542 More architecture-specific flags detailing state of the VCPU that may
6560 The value of the cr8 register. Only valid if in-kernel local APIC is
6567 The value of the APIC BASE msr. Only valid if in-kernel local
6579 reasons. Further architecture-specific information is available in
6591 to unknown reasons. Further architecture-specific information is
6644 executed a memory-mapped I/O instruction which could not be satisfied
6658 has re-entered the kernel with KVM_RUN. The kernel side will first finish
6663 completed before performing a live migration. Userspace can re-enter the
6686 ----------
6697 - ``KVM_HYPERCALL_EXIT_SMC``: Indicates that the guest used the SMC
6701 - ``KVM_HYPERCALL_EXIT_16BIT``: Indicates that the guest used a 16bit
6759 (DAT)
6770 Deprecated - was used for 440 KVM.
6796 This is used on 64-bit PowerPC when emulating a pSeries partition,
6800 the arguments (from the guest R4 - R12). Userspace should put the
6862 a system-level event using some architecture specific mechanism (hypercall
6866 The 'type' field describes the system-level event type.
6869 - KVM_SYSTEM_EVENT_SHUTDOWN -- the guest has requested a shutdown of the
6873 - KVM_SYSTEM_EVENT_RESET -- the guest has requested a reset of the VM.
6876 - KVM_SYSTEM_EVENT_CRASH -- the guest crash occurred and the guest
6880 - KVM_SYSTEM_EVENT_SEV_TERM -- an AMD SEV guest requested termination.
6882 - KVM_SYSTEM_EVENT_TDX_FATAL -- a TDX guest reported a fatal error state.
6883 KVM doesn't do any parsing or conversion, it just dumps 16 general-purpose
6884 registers to userspace, in ascending order of the 4-bit indices for x86-64
6885 general-purpose registers in instruction encoding, as defined in the Intel
6887 - KVM_SYSTEM_EVENT_WAKEUP -- the exiting vCPU is in a suspended state and
6890 - KVM_SYSTEM_EVENT_SUSPEND -- the guest has requested a suspension of
6894 architecture specific information for the system-level event. Only
6897 - for arm64, data[0] is set to KVM_SYSTEM_EVENT_RESET_FLAG_PSCI_RESET2 if
6901 - for arm64, data[0] is set to KVM_SYSTEM_EVENT_SHUTDOWN_FLAG_PSCI_OFF2
6905 - for RISC-V, data[0] is set to the value of the second argument of the
6913 --------------
6923 the call parameters are left in-place in the vCPU registers.
6928 - Honor the guest request to suspend the VM. Userspace can request
6929 in-kernel emulation of suspension by setting the calling vCPU's
6935 - Deny the guest request to suspend the VM. See ARM DEN0022D.b 5.19.2
6951 Indicates that the VCPU's in-kernel local APIC received an EOI for a
6952 level-triggered IOAPIC interrupt. This exit only triggers when the
6994 related to Hyper-V emulation.
6998 - KVM_EXIT_HYPERV_SYNIC -- synchronously notify user-space about
7000 Hyper-V SynIC state change. Notification is used to remap SynIC
7004 - KVM_EXIT_HYPERV_SYNDBG -- synchronously notify user-space about
7006 Hyper-V Synthetic debugger state change. Notification is used to either update
7025 the VM. KVM assumed that if the guest accessed non-memslot memory, it was
7055 __u8 error; /* user -> kernel */
7057 __u32 reason; /* kernel -> user */
7058 __u32 index; /* kernel -> user */
7059 __u64 data; /* kernel <-> user */
7117 - KVM_EXIT_XEN_HCALL -- synchronously notify user-space about Xen hypercall.
7132 done a SBI call which is not handled by KVM RISC-V kernel module. The details
7138 values of SBI call before resuming the VCPU. For more details on RISC-V SBI
7139 spec refer, https://github.com/riscv/riscv-sbi-doc.
7156 - KVM_MEMORY_EXIT_FLAG_PRIVATE - When set, indicates the memory fault occurred
7161 accompanies a return code of '-1', not '0'! errno will always be set to EFAULT
7174 enabled, a VM exit generated if no event window occurs in VM non-root mode
7182 - KVM_NOTIFY_CONTEXT_INVALID -- the VM context is corrupted and not valid
7214 on the Guest-Hypervisor Communication Interface (GHCI) specification;
7217 on re-entry.
7224 * ``TDVMCALL_GET_QUOTE``: the guest has requested to generate a TD-Quote
7225 signed by a service hosting TD-Quoting Enclave operating on the host.
7228 (without the shared bit set) and the size of a shared-memory buffer, in
7232 shared-memory area to check whether the Quote generation is completed or
7300 whether this is a per-vcpu or per-vm capability.
7311 -------------------
7316 :Returns: 0 on success; -1 on error
7320 were invented by Mac-on-Linux to have a standardized communication mechanism
7327 --------------------
7332 :Returns: 0 on success; -1 on error
7348 ------------------
7353 :Returns: 0 on success; -1 on error
7366 addresses of mmu-type-specific data structures. The "array_len" field is an
7382 - The "params" field is of type "struct kvm_book3e_206_tlb_params".
7383 - The "array" field points to an array of type "struct
7385 - The array consists of all entries in the first TLB, followed by all
7387 - Within a TLB, entries are ordered first by increasing set number. Within a
7389 - The hash for determining set number in TLB0 is: (MAS2 >> 12) & (num_sets - 1)
7391 - The tsize field of mas1 shall be set to 4K on TLB0, even though the
7395 ----------------------------
7400 :Returns: 0 on success; -1 on error
7405 handled in-kernel, while the other I/O instructions are passed to userspace.
7410 Note that even though this capability is enabled per-vcpu, the complete
7414 -------------------
7419 :Returns: 0 on success; -1 on error
7433 --------------------
7439 This capability connects the vcpu to an in-kernel MPIC device.
7442 --------------------
7449 This capability connects the vcpu to an in-kernel XICS device.
7452 ------------------------
7458 This capability enables the in-kernel irqchip for s390. Please refer to
7462 --------------------
7476 ---------------------
7489 ----------------------
7494 :Returns: x86: KVM_CHECK_EXTENSION returns a bit-array indicating which register
7510 - the register sets to be copied out to kvm_run are selectable
7512 - vcpu_events are available in addition to regs and sregs.
7515 function as an input bit-array field set by userspace to indicate the
7535 -------------------------
7542 This capability connects the vcpu to an in-kernel XIVE device.
7545 -------------------------
7552 Hyper-V Synthetic interrupt controller(SynIC). Hyper-V SynIC is
7553 used to support Windows Hyper-V based guest paravirt drivers(VMBus).
7558 by the CPU, as it's incompatible with SynIC auto-EOI behavior.
7561 --------------------------
7566 This capability enables a newer version of Hyper-V Synthetic interrupt
7572 -----------------------------------
7577 This capability indicates that KVM running on top of Hyper-V hypervisor
7579 hypercalls are handled by Level 0 hypervisor (Hyper-V) bypassing KVM.
7580 Due to the different ABI for hypercall parameters between Hyper-V and
7583 flush hypercalls by Hyper-V) so userspace should disable KVM identification
7584 in CPUID and only exposes Hyper-V identification. In this case, guest
7585 thinks it's running on Hyper-V and only use Hyper-V hypercalls.
7588 ---------------------------------
7593 When enabled, KVM will disable emulated Hyper-V features provided to the
7594 guest according to the bits Hyper-V CPUID feature leaves. Otherwise, all
7595 currently implemented Hyper-V features are provided unconditionally when
7596 Hyper-V identification is set in the HYPERV_CPUID_INTERFACE (0x40000001)
7600 -------------------------------------
7638 ----------------------------
7642 args[1] is 0 to disable, 1 to enable in-kernel handling
7645 get handled by the kernel or not. Enabling or disabling in-kernel
7647 initial set of hcalls are enabled for in-kernel handling, which
7648 consists of those hcalls for which in-kernel handlers were implemented
7655 If the hcall number specified is not one that has an in-kernel
7660 --------------------------
7669 - SENSE
7670 - SENSE RUNNING
7671 - EXTERNAL CALL
7672 - EMERGENCY SIGNAL
7673 - CONDITIONAL EMERGENCY SIGNAL
7682 ---------------------------------
7690 return -EINVAL if the machine does not support vectors.
7693 --------------------------
7698 This capability allows post-handlers for the STSI instruction. After
7703 vcpu->run::
7714 @addr - guest address of STSI SYSIB
7715 @fc - function code
7716 @sel1 - selector 1
7717 @sel2 - selector 2
7718 @ar - access register number
7720 KVM handlers should exit to userspace with rc = -EREMOTE.
7723 -------------------------
7726 :Parameters: args[0] - number of routes reserved for userspace IOAPICs
7727 :Returns: 0 on success, -1 on error
7737 for the IOAPIC pins. Whenever the LAPIC receives an EOI for these routes,
7744 -------------------
7749 Allows use of runtime-instrumentation introduced with zEC12 processor.
7750 Will return -EINVAL if the machine does not support runtime-instrumentation.
7751 Will return -EBUSY if a VCPU has already been created.
7754 ----------------------
7757 :Parameters: args[0] - features that should be enabled
7758 :Returns: 0 on success, -EINVAL when args[0] contains invalid features
7767 allowing the use of 32-bit APIC IDs. See KVM_CAP_X2APIC_API in their
7774 where 0xff represents CPUs 0-7 in cluster 0.
7777 ----------------------------
7784 mechanism e.g. to realize 2-byte software breakpoints. The kernel will
7792 -------------------
7796 :Returns: 0 on success; -EINVAL if the machine does not support
7797 guarded storage; -EBUSY if a VCPU has already been created.
7802 ---------------------
7807 Allow use of adapter-interruption suppression.
7808 :Returns: 0 on success; -EBUSY if a VCPU has already been created.
7811 --------------------
7829 ----------------------
7841 ------------------------------
7845 :Returns: 0 on success, -EINVAL when args[0] contains invalid exits
7865 --------------------------
7869 :Returns: 0 on success, -EINVAL if hpage module parameter was not set
7877 hpage module parameter is not set to 1, -EINVAL is returned.
7883 ------------------------------
7893 --------------------------
7897 :Returns: 0 on success, -EINVAL when the implementation doesn't support
7898 nested-HV virtualization.
7900 HV-KVM on POWER9 and later systems allows for "nested-HV"
7902 can run using the CPU's supervisor mode (privileged non-hypervisor
7905 kvm-hv module parameter.
7908 ------------------------------
7914 emulated VM-exit when L1 intercepts a #PF exception that occurs in
7915 L2. Similarly, for kvm-intel only, DR6 will not be modified prior to
7916 the emulated VM-exit when L1 intercepts a #DB exception that occurs in
7922 exception.has_payload and to put the faulting address - or the new DR6
7923 bits\ [#]_ - in the exception_payload field.
7934 --------------------------------------
7945 automatically clear and write-protect all pages that are returned as dirty.
7951 KVM_CLEAR_DIRTY_LOG ioctl can operate on a 64-page granularity rather
7976 ------------------------------
7993 ----------------------
7998 :Returns: 0 on success; -1 on error
8001 maximum halt-polling time for all vCPUs in the target VM. This capability can
8003 maximum halt-polling time.
8005 See Documentation/virt/kvm/halt-polling.rst for more information on halt
8009 -------------------------------
8014 :Returns: 0 on success; -1 on error
8041 -------------------------------
8046 :Returns: 0 on success, -EINVAL when args[0] contains invalid bits
8056 the KVM_ENABLE_CAP. The supported modes are mutually-exclusive.
8059 guest, irrespective whether or not the host has enabled split-lock detection
8065 exit, although the host kernel's split-lock #AC detection still applies, if
8071 apply some other policy-based mitigation. When exiting to userspace, KVM sets
8072 KVM_RUN_X86_BUS_LOCK in vcpu-run->flags, and conditionally sets the exit_reason
8077 the next instruction, i.e. the exit is trap-like. On AMD hosts, RIP points at
8078 the offending instruction, i.e. the exit is fault-like.
8085 ----------------------
8089 :Returns: 0 on success, -EINVAL when CPU doesn't support 2nd DAWR
8096 -------------------------------------
8106 This is intended to support in-guest workloads scheduled by the host. This
8107 allows the in-guest workload to maintain its own NPTs and keeps the two vms
8112 --------------------------
8117 :Returns: 0 on success, -EINVAL if the file handle is invalid or if a requested
8135 --------------------------------------
8153 --------------------
8170 ``MAP_ANONYMOUS`` or with a RAM-based file mapping (``tmpfs``, ``memfd``),
8172 -EINVAL return.
8178 -------------------------------------
8188 This is intended to support intra-host migration of VMs between userspace VMMs,
8192 ----------------------------
8194 :Parameters: args[0] - set of KVM quirks to disable
8230 KVM_X86_QUIRK_OUT_7E_INC_RIP By default, KVM pre-increments %rip before
8233 KVM does not pre-increment %rip before
8302 self-snoop, KVM always ignores guest PAT and
8305 when a VM has non-coherent DMA devices
8309 (e.g. ICX, SPR) where self-snoop feature is
8321 ------------------------
8325 :Parameters: args[0] - maximum APIC ID value set for current VM
8326 :Returns: 0 on success, -EINVAL if args[0] is beyond KVM_MAX_VCPU_IDS
8342 ------------------------------
8347 :Returns: 0 on success, -EINVAL if args[0] contains invalid flags or notify
8357 in per-VM scope during VM creation. Notify VM exit is disabled by default.
8360 a VM exit if no event window occurs in VM non-root mode for a specified of
8371 -----------------------------------
8376 :Returns: 0 on success, -EINVAL if args[0] contains an invalid value for the
8377 frequency or if any vCPUs have been created, -ENXIO if a virtual
8380 This capability sets the VM's APIC bus clock frequency, used by KVM's in-kernel
8385 core crystal clock frequency, if a non-zero CPUID 0x15 is exposed to the guest.
8388 ----------------------------------------------------------
8392 :Parameters: args[0] - size of the dirty log ring
8432 00 -----------> 01 -------------> 1X -------+
8435 +------------------------------------------+
8449 using load-acquire/store-release accessors when available, or any
8477 Architecture with TSO-like ordering (such as x86) are allowed to
8483 ring structures can be backed by per-slot bitmaps. With this capability
8493 context. Otherwise, the stand-alone per-slot bitmap mechanism needs to
8506 KVM device "kvm-arm-vgic-its". (2) restore vgic/its tables through
8508 "kvm-arm-vgic-its". VGICv3 LPI pending status is restored. (3) save
8510 command on KVM device "kvm-arm-vgic-v3".
8513 ---------------------------
8518 :Returns: 0 on success, -EINVAL when arg[0] contains invalid bits
8534 -------------------------------------
8539 :Returns: 0 on success, -EPERM if the userspace process does not
8540 have CAP_SYS_BOOT, -EINVAL if args[0] is not 0 or any vCPUs have been
8550 ---------------------------------------
8555 :Returns: 0 on success, -EINVAL if any memslot was already created.
8559 Eager Page Splitting improves the performance of dirty-logging (used
8560 in live migrations) when guest memory is backed by huge-pages. It
8561 avoids splitting huge-pages (into PAGE_SIZE pages) on fault, by doing
8572 64-bit bitmap (each bit describing a block size). The default value is
8576 ---------------------------
8594 -------------------------------
8603 -------------------------------------
8608 :Returns: 0 on success, -EINVAL if vCPUs have been created before enabling this
8621 ---------------------------------
8626 :Returns: 0 on success, -EINVAL if arg[0] is not zero
8638 ---------------------
8644 H_RANDOM hypercall backed by a hardware random-number generator.
8649 -------------------------
8659 ---------------------------
8666 the POWER9 processor), including in-memory segment tables.
8669 -------------------
8699 ----------------------
8713 Both registers and addresses are 32-bits wide.
8714 It will only be possible to run 32-bit guest code.
8716 1 MIPS64 or microMIPS64 with access only to 32-bit compatibility segments.
8717 Registers are 64-bits wide, but addresses are 32-bits wide.
8718 64-bit guest code may run but cannot access MIPS64 memory segments.
8719 It will also be possible to run 32-bit guest code.
8722 Both registers and addresses are 64-bits wide.
8723 It will be possible to run 64-bit or 32-bit guest code.
8727 ------------------------
8732 that if userspace creates a VM without an in-kernel interrupt controller, it
8733 will be notified of changes to the output level of in-kernel emulated devices,
8736 updates the vcpu's run->s.regs.device_irq_level field to represent the actual
8742 userspace can always sample the device output level and re-compute the state of
8744 of run->s.regs.device_irq_level on every kvm exit.
8745 The value in run->s.regs.device_irq_level can represent both level and edge
8747 signals will exit to userspace with the bit in run->s.regs.device_irq_level
8750 The field run->s.regs.device_irq_level is available independent of
8751 run->kvm_valid_regs or run->kvm_dirty_regs bits.
8755 and thereby which bits in run->s.regs.device_irq_level can signal values.
8761 KVM_ARM_DEV_EL1_VTIMER - EL1 virtual timer
8762 KVM_ARM_DEV_EL1_PTIMER - EL1 physical timer
8763 KVM_ARM_DEV_PMU - ARM PMU overflow interrupt signal
8770 -----------------------------
8780 ----------------------------
8790 -------------------------------
8799 ---------------------
8806 ----------------------
8815 ---------------------
8820 use copy-on-write semantics as well as dirty pages tracking via read-only page
8824 ---------------------
8833 ----------------------------
8837 This capability indicates that KVM supports paravirtualized Hyper-V TLB Flush
8843 ----------------------------------
8858 ----------------------------
8862 This capability indicates that KVM supports paravirtualized Hyper-V IPI send
8867 -----------------------------
8875 ---------------------------
8886 -----------------------
8892 architecture-specific interfaces. This capability and the architecture-
8899 -------------------------
8909 an 8-byte value consisting of a one-byte Control Program Name Code (CPNC) and
8910 a 7-byte Control Program Version Code (CPVC). The CPNC determines what
8919 -------------------------------
8930 ---------------------------
8944 --------------------
8974 The KVM_XEN_HVM_CONFIG_RUNSTATE flag indicates that the runstate-related
9008 ---------------------------
9022 IBM pSeries (sPAPR) guest starts using them if "hcall-multi-tce" is
9023 present in the "ibm,hypertas-functions" device-tree property.
9033 --------------------
9042 --------------------------------
9054 ------------------------------
9074 When getting the Modified Change Topology Report value, the attr->addr
9078 ---------------------
9083 This capability returns a bitmap of support VM types. The 1-setting of bit @n
9093 production. The behavior and effective ABI for software-protected VMs is
9097 -------------------------------
9106 IBM pSeries (sPAPR) guest starts using it if "hcall-rpt-invalidate" is
9107 present in the "ibm,hypertas-functions" device-tree property.
9113 ---------------------------
9121 This capability allows a guest kernel to use a better-performance mode for
9125 ------------------------------
9130 kvm_run.memory_fault if KVM cannot resolve a guest page fault VM-Exit, e.g. if
9145 ---------------------------
9168 --------
9182 ``KVM_ENABLE_CAP(KVM_CAP_IRQCHIP_SPLIT)`` are used to enable in-kernel emulation of
9189 is present and the kernel has enabled in-kernel emulation of the local APIC.