Lines Matching full:capability
96 Capability:
102 support this ioctl, there's no capability bit to check its
124 :Capability: basic
141 :Capability: basic
175 is dependent on the CPU capability and the kernel configuration. The limit can
182 Please note that configuring the IPA size does not affect the capability
191 :Capability: basic, KVM_CAP_GET_MSR_FEATURES for KVM_GET_MSR_FEATURE_INDEX_LIST
233 :Capability: basic, KVM_CAP_CHECK_EXTENSION_VM for vm ioctl
252 :Capability: basic
278 :Capability: basic
290 :Capability: basic
318 same partition.) The KVM_CAP_PPC_SMT capability indicates the number
337 :Capability: basic
366 see the description of the capability.
374 :Capability: basic
386 :Capability: basic
413 :Capability: basic
446 :Capability: basic
460 :Capability: basic
491 :Capability: basic
504 :Capability: basic
531 :Capability: basic
622 :Capability: basic
634 :Capability: basic (vcpu), KVM_CAP_GET_MSR_FEATURES (system)
674 :Capability: basic
696 :Capability: basic
736 :Capability: basic
762 :Capability: basic
791 :Capability: basic
820 :Capability: KVM_CAP_IRQCHIP, KVM_CAP_S390_IRQCHIP (s390)
835 Note that on s390 the KVM_CAP_S390_IRQCHIP vm capability needs to be enabled
842 :Capability: KVM_CAP_IRQCHIP
863 capability is present (or unless it is not using the in-kernel irqchip,
893 Note that on arm64, the KVM_CAP_IRQCHIP capability only conditions
911 :Capability: KVM_CAP_IRQCHIP
936 :Capability: KVM_CAP_IRQCHIP
961 :Capability: KVM_CAP_XEN_HVM
1007 :Capability: KVM_CAP_ADJUST_CLOCK
1057 :Capability: KVM_CAP_ADJUST_CLOCK
1092 :Capability: KVM_CAP_VCPU_EVENTS
1215 :Capability: KVM_CAP_VCPU_EVENTS
1282 :Capability: KVM_CAP_DEBUGREGS
1304 :Capability: KVM_CAP_DEBUGREGS
1319 :Capability: KVM_CAP_USER_MEMORY
1348 KVM_CAP_MULTI_ADDRESS_SPACE capability. Slots in separate address spaces
1371 use it. The latter can be set, if KVM_CAP_READONLY_MEM capability allows it,
1375 When the KVM_CAP_SYNC_MMU capability is available, changes in the backing of
1388 :Capability: KVM_CAP_SET_TSS_ADDR
1408 :Capability: KVM_CAP_ENABLE_CAP
1414 :Capability: KVM_CAP_ENABLE_CAP_VM
1428 To check if a capability can be enabled, the KVM_CHECK_EXTENSION ioctl should
1437 The capability that is supposed to get enabled.
1463 :Capability: KVM_CAP_MP_STATE
1541 :Capability: KVM_CAP_MP_STATE
1563 :Capability: KVM_CAP_SET_IDENTITY_MAP_ADDR
1587 :Capability: KVM_CAP_SET_BOOT_CPU_ID
1602 :Capability: KVM_CAP_XSAVE
1622 :Capability: KVM_CAP_XSAVE and KVM_CAP_XSAVE2
1650 :Capability: KVM_CAP_XCRS
1677 :Capability: KVM_CAP_XCRS
1704 :Capability: KVM_CAP_EXT_CPUID
1793 :Capability: KVM_CAP_PPC_GET_PVINFO
1823 :Capability: KVM_CAP_IRQ_ROUTING
1873 KVM_CAP_MSI_DEVID capability advertises the requirement to provide
1874 the device ID. If this capability is not available, userspace should
1900 feature of KVM_CAP_X2APIC_API capability is enabled. If it is enabled,
1937 :Capability: KVM_CAP_TSC_CONTROL / KVM_CAP_VM_TSC_CONTROL
1946 If the KVM_CAP_VM_TSC_CONTROL capability is advertised, this can also
1953 :Capability: KVM_CAP_GET_TSC_KHZ / KVM_CAP_VM_TSC_CONTROL
1967 :Capability: KVM_CAP_IRQCHIP
1998 :Capability: KVM_CAP_IRQCHIP
2015 regs field) depends on the state of the KVM_CAP_X2APIC_API capability.
2022 :Capability: KVM_CAP_IOEVENTFD
2068 :Capability: KVM_CAP_SW_TLB
2104 :Capability: KVM_CAP_SPAPR_TCE
2113 and provides a scatter/gather capability for PAPR virtual I/O.
2143 :Capability: KVM_CAP_PPC_RMA
2170 The KVM_CAP_PPC_RMA capability is 1 or 2 if the KVM_ALLOCATE_RMA ioctl
2179 :Capability: KVM_CAP_USER_NMI
2206 :Capability: KVM_CAP_S390_UCONTROL
2228 :Capability: KVM_CAP_S390_UCONTROL
2250 :Capability: KVM_CAP_S390_UCONTROL
2268 :Capability: KVM_CAP_ONE_REG
2865 :Capability: KVM_CAP_ONE_REG
2895 :Capability: KVM_CAP_KVMCLOCK_CTRL
2919 :Capability: KVM_CAP_SIGNAL_MSI
2941 KVM_CAP_MSI_DEVID capability advertises the requirement to provide
2942 the device ID. If this capability is not available, userspace
2950 feature of KVM_CAP_X2APIC_API capability is enabled. If it is enabled,
2958 :Capability: KVM_CAP_PIT2
2991 :Capability: KVM_CAP_PIT_STATE2
3019 :Capability: KVM_CAP_PIT_STATE2
3034 :Capability: KVM_CAP_PPC_GET_SMMU_INFO
3109 :Capability: KVM_CAP_IRQFD
3148 :Capability: KVM_CAP_PPC_ALLOC_HTAB
3157 virtualization. Otherwise the capability doesn't exist and the ioctl
3185 :Capability: basic
3240 :Capability: KVM_CAP_PPC_HTAB_FD
3295 :Capability: KVM_CAP_DEVICE_CTRL
3333 :Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device,
3369 :Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device,
3391 :Capability: basic
3489 :Capability: basic
3518 :Capability: basic
3545 :Capability: KVM_CAP_ARM_SET_DEVICE_ADDR
3594 :Capability: KVM_CAP_PPC_RTAS
3614 :Capability: KVM_CAP_SET_GUEST_DEBUG
3662 For ppc, the KVM_CAP_PPC_GUEST_DEBUG_SSTEP capability indicates whether
3665 Also when supported, KVM_CAP_SET_GUEST_DEBUG2 capability indicates the
3675 :Capability: KVM_CAP_EXT_EMUL_CPUID
3750 :Capability: KVM_CAP_S390_MEM_OP, KVM_CAP_S390_PROTECTED, KVM_CAP_S390_MEM_OP_EXTENSION
3759 The KVM_CAP_S390_MEM_OP_EXTENSION capability specifies what functionality is
3783 KVM_CAP_S390_MEM_OP capability. "buf" is the buffer supplied by the
3864 SIDA accesses are available if the KVM_CAP_S390_PROTECTED capability is available.
3873 :Capability: KVM_CAP_S390_SKEYS
3905 :Capability: KVM_CAP_S390_SKEYS
3933 :Capability: KVM_CAP_S390_INJECT_IRQ
3993 :Capability: KVM_CAP_S390_IRQ_STATE
4028 :Capability: KVM_CAP_S390_IRQ_STATE
4066 :Capability: KVM_CAP_X86_SMM
4077 :Capability: KVM_CAP_X86_MSR_FILTER
4184 :Capability: KVM_CAP_SPAPR_TCE_64
4193 This capability uses extended struct in ioctl interface::
4217 :Capability: KVM_CAP_REINJECT_CONTROL
4244 :Capability: KVM_CAP_PPC_RADIX_MMU or KVM_CAP_PPC_HASH_MMU_V3
4278 :Capability: KVM_CAP_PPC_RADIX_MMU
4315 :Capability: KVM_CAP_SPAPR_RESIZE_HPT
4369 :Capability: KVM_CAP_SPAPR_RESIZE_HPT
4414 :Capability: KVM_CAP_MCE
4427 :Capability: KVM_CAP_MCE
4434 -EINVAL if requested MCE capability is not supported.
4446 :Capability: KVM_CAP_MCE
4480 :Capability: KVM_CAP_S390_CMMA_MIGRATION
4575 :Capability: KVM_CAP_S390_CMMA_MIGRATION
4623 :Capability: KVM_CAP_PPC_GET_CPU_CHAR
4670 :Capability: basic
4687 :Capability: basic
4711 :Capability: basic
4723 :Capability: KVM_CAP_HYPERV_EVENTFD
4758 :Capability: KVM_CAP_NESTED_STATE
4832 :Capability: KVM_CAP_NESTED_STATE
4844 :Capability: KVM_CAP_COALESCED_MMIO (for coalesced mmio)
4873 :Capability: KVM_CAP_MANUAL_DIRTY_LOG_PROTECT2
4908 is enabled; for more information, see the description of the capability.
4915 :Capability: KVM_CAP_HYPERV_CPUID (vcpu), KVM_CAP_SYS_HYPERV_CPUID (system)
5028 :Capability: KVM_CAP_PMU_EVENT_FILTER
5062 :Capability: basic
5086 :Capability: KVM_CAP_S390_VCPU_RESETS
5098 :Capability: none
5111 :Capability: KVM_CAP_S390_VCPU_RESETS
5125 :Capability: KVM_CAP_S390_PROTECTED
5183 :Capability: KVM_CAP_S390_PROTECTED_DUMP
5248 :Capability: KVM_CAP_S390_PROTECTED_DUMP
5295 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5389 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5402 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5496 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5511 :Capability: KVM_CAP_ARM_MTE
5548 :Capability: KVM_CAP_SREGS2
5581 :Capability: KVM_CAP_SREGS2
5594 :Capability: KVM_CAP_STATS_BINARY_FD
5797 :Capability: KVM_CAP_XSAVE2
5824 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_EVTCHN_SEND
5844 :Capability: KVM_CAP_S390_PROTECTED_DUMP
5869 :Capability: KVM_CAP_S390_ZPCI_OP
6308 KVM_CAP_ARM_SYSTEM_SUSPEND VM capability. If a guest invokes the PSCI
6419 this capability at VM creation. Once this is done, these types of errors will
6441 Used on x86 systems. When the VM capability KVM_CAP_X86_USER_SPACE_MSR is
6524 Used on x86 systems. When the VM capability KVM_CAP_X86_NOTIFY_VMEXIT is
6589 whether this is a per-vcpu or per-vm capability.
6592 what parameters are accepted by the capability.
6607 This capability enables interception of OSI hypercalls that otherwise would
6612 When this capability is enabled, KVM_EXIT_OSI can occur.
6623 This capability enables interception of PAPR hypercalls. PAPR hypercalls are
6633 When this capability is enabled, KVM_EXIT_PAPR_HCALL can occur.
6691 This capability enables support for handling of channel I/O instructions.
6696 When this capability is enabled, KVM_EXIT_S390_TSCH will occur on TEST
6699 Note that even though this capability is enabled per-vcpu, the complete
6710 This capability enables or disables the delivery of interrupts through the
6719 When this capability is enabled, KVM_EXIT_EPR can occur.
6728 This capability connects the vcpu to an in-kernel MPIC device.
6738 This capability connects the vcpu to an in-kernel XICS device.
6747 This capability enables the in-kernel irqchip for s390. Please refer to
6757 This capability allows the use of the host Floating Point Unit by the guest. It
6771 This capability allows the use of the MIPS SIMD Architecture (MSA) by the guest.
6831 This capability connects the vcpu to an in-kernel XIVE device.
6848 what parameters are accepted by the capability.
6862 This capability controls whether individual sPAPR hypercalls (hcalls)
6867 before this capability was implemented. If disabled, the kernel will
6883 This capability controls which SIGP orders will be handled completely in user
6884 space. With this capability enabled, all fast orders will be handled completely
6896 in the hardware prior to interception). If this capability is not enabled, the
6916 This capability allows post-handlers for the STSI instruction. After
6952 This capability also enables in kernel routing of interrupt requests;
7000 With this capability enabled, all illegal instructions 0x0000 (2 bytes) will
7006 This capability can be enabled dynamically even if VCPUs were already
7034 Enabling this capability on a VM provides userspace with a way to set
7039 be 0. A successful call to enable this capability will result in
7040 vsmt_mode being returned when the KVM_CAP_PPC_SMT capability is
7041 subsequently queried for the VM. This capability is only supported by
7043 The KVM_CAP_PPC_SMT_POSSIBLE capability indicates which virtual SMT
7052 With this capability a machine check exception in the guest address
7055 machine check handling routine. Without this capability KVM will
7072 Enabling this capability on a VM provides userspace with a way to no
7090 With this capability the KVM support for memory backing with 1m pages
7091 through hugetlbfs can be enabled for a VM. After the capability is
7097 this capability, the VM will not be able to run.
7105 With this capability, a guest may read the MSR_PLATFORM_INFO MSR. Otherwise,
7107 capability does not enable write permissions of this MSR for the guest.
7120 state). Enabling this capability on a VM depends on the CPU having
7130 With this capability enabled, CR2 will not be modified prior to the
7142 This capability also enables exception.pending in struct
7196 This capability indicates that KVM is running on a host that has
7204 If present, this capability can be enabled for a VM, meaning that KVM
7217 maximum halt-polling time for all vCPUs in the target VM. This capability can
7232 This capability enables trapping of #GP invoking RDMSR and WRMSR instructions
7240 this capability. With it enabled, MSR accesses that match the mask specified in
7259 Enabling this capability on a VM provides userspace with a way to select
7275 This capability is aimed to address the thread that VM can exploit bus locks to
7277 capability and select the KVM_BUS_LOCK_DETECTION_EXIT mode, KVM will set the
7290 This capability can be used to check / enable 2nd DAWR feature provided
7302 This capability enables userspace to copy encryption context from the vm
7336 :Capability: KVM_CAP_PPC_RPT_INVALIDATE
7340 This capability indicates that the kernel is capable of handling
7348 This capability is enabled for hypervisors on platforms like POWER9
7357 When this capability is enabled, an emulation failure will result in an exit
7375 This capability indicates that KVM (and the hardware) supports exposing the
7378 available to a guest running in AArch64 mode and enabling this capability will
7386 When this capability is enabled all memory in memslots must be mapped as
7401 This capability enables userspace to migrate the encryption context from the VM
7410 :Capability: KVM_CAP_PPC_AIL_MODE_3
7414 This capability indicates that the kernel supports the mode 3 setting for the
7418 This capability allows a guest kernel to use a better-performance mode for
7424 :Capability: KVM_CAP_DISABLE_QUIRKS2
7429 This capability, if enabled, will cause KVM to disable some behavior
7432 Calling KVM_CHECK_EXTENSION for this capability returns a bitmask of
7435 The argument to KVM_ENABLE_CAP for this capability is a bitmask of
7502 This capability allows userspace to specify maximum possible APIC ID
7529 This capability allows userspace to configure the notify VM exit on/off
7539 This capability is aimed to mitigate the threat that malicious VMs can
7554 This capability, if KVM_CHECK_EXTENSION indicates that it is
7558 with the KVM_CAP_PPC_ENABLE_HCALL capability.
7565 This capability, if KVM_CHECK_EXTENSION indicates that it is
7571 capability via KVM_ENABLE_CAP ioctl on the vcpu fd. Note that this
7580 This capability, if KVM_CHECK_EXTENSION indicates that it is
7590 This capability, if KVM_CHECK_EXTENSION indicates that it is
7600 This capability, if KVM_CHECK_EXTENSION on the main kvm handle indicates that
7606 If KVM_CHECK_EXTENSION on a kvm VM handle indicates that this capability is
7630 This capability, if KVM_CHECK_EXTENSION on the main kvm handle indicates that
7636 If KVM_CHECK_EXTENSION on a kvm VM handle indicates that this capability is
7644 This capability indicates the supported architecture type of the guest, i.e. the
7647 The values returned when this capability is checked by KVM_CHECK_EXTENSION on a
7672 This capability, if KVM_CHECK_EXTENSION indicates that it is available, means
7695 number larger than 0 indicating the version of this capability is implemented
7715 Querying this capability returns a bitmap indicating the possible
7725 This capability enables a newer version of Hyper-V Synthetic interrupt
7735 This capability indicates that userspace can load HV_X64_MSR_VP_INDEX msr. Its
7738 capability is absent, userspace can still query this msr's value.
7746 This capability indicates if the flic device will be able to get/set the
7755 This capability indicates that the PSW is exposed via the kvm_run structure.
7762 This capability indicates that the user space memory used as guest mapping can
7771 This capability indicates that the user space memory used as guest mapping can
7780 This capability indicates that kvm will implement the interfaces to handle
7782 facility 82 should not be provided to the guest without this capability.
7789 This capability indicates that KVM supports paravirtualized Hyper-V TLB Flush
7799 This capability indicates that userspace can specify (via the
7802 If KVM advertises this capability, userspace can only specify the ISS field for
7814 This capability indicates that KVM supports paravirtualized Hyper-V IPI send
7823 This capability indicates that KVM running on top of Hyper-V hypervisor
7827 KVM, enabling this capability effectively disables all hypercall
7838 This capability indicates that the KVM_S390_NORMAL_RESET and
7846 This capability indicates that the Ultravisor has been initialized and
7848 This capability governs the KVM_S390_PV_COMMAND ioctl and the
7857 This capability indicates that KVM supports steal time accounting.
7859 architecture-specific interfaces. This capability and the architecture-
7870 This capability enables a guest to set information about its control program
7882 If this capability is available, then the CPNC and CPVC can be synchronized
7890 This capability indicates that KVM supports deflection of MSR reads and
7901 This capability indicates that KVM supports that accesses to user defined MSRs
7902 may be rejected. With this capability exposed, KVM exports new VM ioctl
7946 ioctl to enable this capability for the new guest and set the size of
7947 the rings. Enabling the capability is only allowed before creating any
8005 NOTE: the capability KVM_CAP_DIRTY_LOG_RING and the corresponding
8012 NOTE: KVM_CAP_DIRTY_LOG_RING_ACQ_REL is the only capability that
8025 This capability indicates the features that Xen supports for hosting Xen
8068 :Capability: KVM_CAP_PPC_MULTITCE
8072 This capability means the kernel is capable of handling hypercalls
8089 This capability is always enabled.
8096 This capability indicates that the KVM virtual PTP service is
8114 :Capability: KVM_CAP_EXIT_HYPERCALL
8118 This capability, if enabled, will cause KVM to exit to userspace
8121 Calling KVM_CHECK_EXTENSION for this capability will return a bitmask
8133 :Capability KVM_CAP_PMU_CAPABILITY
8139 This capability alters PMU virtualization in KVM.
8141 Calling KVM_CHECK_EXTENSION for this capability returns a bitmask of
8148 At this time, KVM_PMU_CAP_DISABLE is the only capability. Setting
8149 this capability will disable PMU virtualization for that VM. Usermode
8155 :Capability: KVM_CAP_ARM_SYSTEM_SUSPEND
8165 :Capability: KVM_CAP_S390_PROTECTED_DUMP
8169 This capability indicates that KVM and the Ultravisor support dumping
8178 :Capability: KVM_CAP_VM_DISABLE_NX_HUGE_PAGES
8186 This capability disables the NX huge pages mitigation for iTLB MULTIHIT.
8188 The capability has no effect if the nx_huge_pages module parameter is not set.
8190 This capability may only be set before any vCPUs are created.
8195 :Capability: KVM_CAP_S390_CPU_TOPOLOGY
8199 This capability indicates that KVM will provide the S390 CPU Topology
8206 to the guest without this capability.
8208 When this capability is present, KVM provides a new attribute group