Lines Matching full:capability
96 Capability:
102 support this ioctl, there's no capability bit to check its
124 :Capability: basic
141 :Capability: basic
194 is dependent on the CPU capability and the kernel configuration. The limit can
201 Please note that configuring the IPA size does not affect the capability
210 :Capability: basic, KVM_CAP_GET_MSR_FEATURES for KVM_GET_MSR_FEATURE_INDEX_LIST
252 :Capability: basic, KVM_CAP_CHECK_EXTENSION_VM for vm ioctl
271 :Capability: basic
297 :Capability: basic
325 same partition.) The KVM_CAP_PPC_SMT capability indicates the number
344 :Capability: basic
373 see the description of the capability.
382 :Capability: basic
409 :Capability: basic
449 :Capability: basic
463 :Capability: basic
494 :Capability: basic
507 :Capability: basic
534 :Capability: basic
633 :Capability: basic (vcpu), KVM_CAP_GET_MSR_FEATURES (system)
673 :Capability: basic
695 :Capability: basic
735 :Capability: basic
761 :Capability: basic
799 :Capability: basic
837 :Capability: KVM_CAP_IRQCHIP, KVM_CAP_S390_IRQCHIP (s390)
852 Note that on s390 the KVM_CAP_S390_IRQCHIP vm capability needs to be enabled
859 :Capability: KVM_CAP_IRQCHIP
880 capability is present (or unless it is not using the in-kernel irqchip,
910 Note that on arm64, the KVM_CAP_IRQCHIP capability only conditions
928 :Capability: KVM_CAP_IRQCHIP
953 :Capability: KVM_CAP_IRQCHIP
978 :Capability: KVM_CAP_XEN_HVM
1024 :Capability: KVM_CAP_ADJUST_CLOCK
1074 :Capability: KVM_CAP_ADJUST_CLOCK
1109 :Capability: KVM_CAP_VCPU_EVENTS
1232 :Capability: KVM_CAP_VCPU_EVENTS
1299 :Capability: KVM_CAP_DEBUGREGS
1321 :Capability: KVM_CAP_DEBUGREGS
1336 :Capability: KVM_CAP_USER_MEMORY
1365 KVM_CAP_MULTI_ADDRESS_SPACE capability. Slots in separate address spaces
1388 use it. The latter can be set, if KVM_CAP_READONLY_MEM capability allows it,
1392 When the KVM_CAP_SYNC_MMU capability is available, changes in the backing of
1409 :Capability: KVM_CAP_SET_TSS_ADDR
1429 :Capability: KVM_CAP_ENABLE_CAP
1435 :Capability: KVM_CAP_ENABLE_CAP_VM
1449 To check if a capability can be enabled, the KVM_CHECK_EXTENSION ioctl should
1458 The capability that is supposed to get enabled.
1484 :Capability: KVM_CAP_MP_STATE
1565 :Capability: KVM_CAP_MP_STATE
1590 :Capability: KVM_CAP_SET_IDENTITY_MAP_ADDR
1614 :Capability: KVM_CAP_SET_BOOT_CPU_ID
1629 :Capability: KVM_CAP_XSAVE
1649 :Capability: KVM_CAP_XSAVE and KVM_CAP_XSAVE2
1677 :Capability: KVM_CAP_XCRS
1704 :Capability: KVM_CAP_XCRS
1731 :Capability: KVM_CAP_EXT_CPUID
1820 :Capability: KVM_CAP_PPC_GET_PVINFO
1850 :Capability: KVM_CAP_IRQ_ROUTING
1900 KVM_CAP_MSI_DEVID capability advertises the requirement to provide
1901 the device ID. If this capability is not available, userspace should
1927 feature of KVM_CAP_X2APIC_API capability is enabled. If it is enabled,
1964 :Capability: KVM_CAP_TSC_CONTROL / KVM_CAP_VM_TSC_CONTROL
1973 If the KVM_CAP_VM_TSC_CONTROL capability is advertised, this can also
1980 :Capability: KVM_CAP_GET_TSC_KHZ / KVM_CAP_VM_TSC_CONTROL
1994 :Capability: KVM_CAP_IRQCHIP
2025 :Capability: KVM_CAP_IRQCHIP
2042 regs field) depends on the state of the KVM_CAP_X2APIC_API capability.
2049 :Capability: KVM_CAP_IOEVENTFD
2095 :Capability: KVM_CAP_SW_TLB
2131 :Capability: KVM_CAP_SPAPR_TCE
2140 and provides a scatter/gather capability for PAPR virtual I/O.
2170 :Capability: KVM_CAP_PPC_RMA
2197 The KVM_CAP_PPC_RMA capability is 1 or 2 if the KVM_ALLOCATE_RMA ioctl
2206 :Capability: KVM_CAP_USER_NMI
2233 :Capability: KVM_CAP_S390_UCONTROL
2255 :Capability: KVM_CAP_S390_UCONTROL
2277 :Capability: KVM_CAP_S390_UCONTROL
2295 :Capability: KVM_CAP_ONE_REG
2907 :Capability: KVM_CAP_ONE_REG
2937 :Capability: KVM_CAP_KVMCLOCK_CTRL
2961 :Capability: KVM_CAP_SIGNAL_MSI
2983 KVM_CAP_MSI_DEVID capability advertises the requirement to provide
2984 the device ID. If this capability is not available, userspace
2992 feature of KVM_CAP_X2APIC_API capability is enabled. If it is enabled,
3000 :Capability: KVM_CAP_PIT2
3033 :Capability: KVM_CAP_PIT_STATE2
3061 :Capability: KVM_CAP_PIT_STATE2
3076 :Capability: KVM_CAP_PPC_GET_SMMU_INFO
3151 :Capability: KVM_CAP_IRQFD
3190 :Capability: KVM_CAP_PPC_ALLOC_HTAB
3199 virtualization. Otherwise the capability doesn't exist and the ioctl
3227 :Capability: basic
3282 :Capability: KVM_CAP_PPC_HTAB_FD
3337 :Capability: KVM_CAP_DEVICE_CTRL
3376 :Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device,
3413 :Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device,
3437 :Capability: basic
3535 :Capability: basic
3564 :Capability: basic
3591 :Capability: KVM_CAP_ARM_SET_DEVICE_ADDR
3640 :Capability: KVM_CAP_PPC_RTAS
3660 :Capability: KVM_CAP_SET_GUEST_DEBUG
3708 For ppc, the KVM_CAP_PPC_GUEST_DEBUG_SSTEP capability indicates whether
3711 Also when supported, KVM_CAP_SET_GUEST_DEBUG2 capability indicates the
3721 :Capability: KVM_CAP_EXT_EMUL_CPUID
3796 :Capability: KVM_CAP_S390_MEM_OP, KVM_CAP_S390_PROTECTED, KVM_CAP_S390_MEM_OP_EXTENSION
3805 The KVM_CAP_S390_MEM_OP_EXTENSION capability specifies what functionality is
3831 KVM_CAP_S390_MEM_OP capability. "buf" is the buffer supplied by the
3932 SIDA accesses are available if the KVM_CAP_S390_PROTECTED capability is available.
3941 :Capability: KVM_CAP_S390_SKEYS
3973 :Capability: KVM_CAP_S390_SKEYS
4001 :Capability: KVM_CAP_S390_INJECT_IRQ
4061 :Capability: KVM_CAP_S390_IRQ_STATE
4096 :Capability: KVM_CAP_S390_IRQ_STATE
4134 :Capability: KVM_CAP_X86_SMM
4145 :Capability: KVM_CAP_X86_MSR_FILTER
4243 :Capability: KVM_CAP_SPAPR_TCE_64
4252 This capability uses extended struct in ioctl interface::
4276 :Capability: KVM_CAP_REINJECT_CONTROL
4303 :Capability: KVM_CAP_PPC_RADIX_MMU or KVM_CAP_PPC_HASH_MMU_V3
4337 :Capability: KVM_CAP_PPC_RADIX_MMU
4374 :Capability: KVM_CAP_SPAPR_RESIZE_HPT
4428 :Capability: KVM_CAP_SPAPR_RESIZE_HPT
4473 :Capability: KVM_CAP_MCE
4486 :Capability: KVM_CAP_MCE
4493 -EINVAL if requested MCE capability is not supported.
4505 :Capability: KVM_CAP_MCE
4539 :Capability: KVM_CAP_S390_CMMA_MIGRATION
4640 :Capability: KVM_CAP_S390_CMMA_MIGRATION
4688 :Capability: KVM_CAP_PPC_GET_CPU_CHAR
4735 :Capability: basic
4752 :Capability: basic
4776 :Capability: basic
4788 :Capability: KVM_CAP_HYPERV_EVENTFD
4823 :Capability: KVM_CAP_NESTED_STATE
4897 :Capability: KVM_CAP_NESTED_STATE
4909 :Capability: KVM_CAP_COALESCED_MMIO (for coalesced mmio)
4938 :Capability: KVM_CAP_MANUAL_DIRTY_LOG_PROTECT2
4973 is enabled; for more information, see the description of the capability.
4980 :Capability: KVM_CAP_HYPERV_CPUID (vcpu), KVM_CAP_SYS_HYPERV_CPUID (system)
5093 :Capability: KVM_CAP_PMU_EVENT_FILTER
5140 :Capability: KVM_CAP_PMU_EVENT_MASKED_EVENTS
5209 :Capability: basic
5233 :Capability: KVM_CAP_S390_VCPU_RESETS
5245 :Capability: none
5258 :Capability: KVM_CAP_S390_VCPU_RESETS
5272 :Capability: KVM_CAP_S390_PROTECTED
5333 :Capability: KVM_CAP_S390_PROTECTED_DUMP
5398 :Capability: KVM_CAP_S390_PROTECTED_DUMP
5443 :Capability: KVM_CAP_S390_PROTECTED_ASYNC_DISABLE
5460 :Capability: KVM_CAP_S390_PROTECTED_ASYNC_DISABLE
5475 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5584 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5597 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5696 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5711 :Capability: KVM_CAP_ARM_MTE
5749 :Capability: KVM_CAP_SREGS2
5782 :Capability: KVM_CAP_SREGS2
5795 :Capability: KVM_CAP_STATS_BINARY_FD
5998 :Capability: KVM_CAP_XSAVE2
6025 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_EVTCHN_SEND
6045 :Capability: KVM_CAP_S390_PROTECTED_DUMP
6070 :Capability: KVM_CAP_S390_ZPCI_OP
6117 :Capability: KVM_CAP_COUNTER_OFFSET
6123 This capability indicates that userspace is able to apply a single VM-wide
6157 :Capability: KVM_CAP_ARM_SUPPORTED_REG_MASK_RANGES
6183 capability returns the supported ranges, expressed as a set of flags. Each
6205 :Capability: KVM_CAP_USER_MEMORY2
6250 :Capability: KVM_CAP_MEMORY_ATTRIBUTES
6286 :Capability: KVM_CAP_GUEST_MEMFD
6746 KVM_CAP_ARM_SYSTEM_SUSPEND VM capability. If a guest invokes the PSCI
6857 this capability at VM creation. Once this is done, these types of errors will
6879 Used on x86 systems. When the VM capability KVM_CAP_X86_USER_SPACE_MSR is
6990 Used on x86 systems. When the VM capability KVM_CAP_X86_NOTIFY_VMEXIT is
7050 whether this is a per-vcpu or per-vm capability.
7053 what parameters are accepted by the capability.
7068 This capability enables interception of OSI hypercalls that otherwise would
7073 When this capability is enabled, KVM_EXIT_OSI can occur.
7084 This capability enables interception of PAPR hypercalls. PAPR hypercalls are
7094 When this capability is enabled, KVM_EXIT_PAPR_HCALL can occur.
7152 This capability enables support for handling of channel I/O instructions.
7157 When this capability is enabled, KVM_EXIT_S390_TSCH will occur on TEST
7160 Note that even though this capability is enabled per-vcpu, the complete
7171 This capability enables or disables the delivery of interrupts through the
7180 When this capability is enabled, KVM_EXIT_EPR can occur.
7189 This capability connects the vcpu to an in-kernel MPIC device.
7199 This capability connects the vcpu to an in-kernel XICS device.
7208 This capability enables the in-kernel irqchip for s390. Please refer to
7218 This capability allows the use of the host Floating Point Unit by the guest. It
7232 This capability allows the use of the MIPS SIMD Architecture (MSA) by the guest.
7292 This capability connects the vcpu to an in-kernel XIVE device.
7309 what parameters are accepted by the capability.
7323 This capability controls whether individual sPAPR hypercalls (hcalls)
7328 before this capability was implemented. If disabled, the kernel will
7344 This capability controls which SIGP orders will be handled completely in user
7345 space. With this capability enabled, all fast orders will be handled completely
7357 in the hardware prior to interception). If this capability is not enabled, the
7377 This capability allows post-handlers for the STSI instruction. After
7413 This capability also enables in kernel routing of interrupt requests;
7461 With this capability enabled, all illegal instructions 0x0000 (2 bytes) will
7467 This capability can be enabled dynamically even if VCPUs were already
7495 Enabling this capability on a VM provides userspace with a way to set
7500 be 0. A successful call to enable this capability will result in
7501 vsmt_mode being returned when the KVM_CAP_PPC_SMT capability is
7502 subsequently queried for the VM. This capability is only supported by
7504 The KVM_CAP_PPC_SMT_POSSIBLE capability indicates which virtual SMT
7513 With this capability a machine check exception in the guest address
7516 machine check handling routine. Without this capability KVM will
7533 Enabling this capability on a VM provides userspace with a way to no
7551 With this capability the KVM support for memory backing with 1m pages
7552 through hugetlbfs can be enabled for a VM. After the capability is
7558 this capability, the VM will not be able to run.
7566 With this capability, a guest may read the MSR_PLATFORM_INFO MSR. Otherwise,
7568 capability does not enable write permissions of this MSR for the guest.
7581 state). Enabling this capability on a VM depends on the CPU having
7591 With this capability enabled, CR2 will not be modified prior to the
7603 This capability also enables exception.pending in struct
7658 This capability indicates that KVM is running on a host that has
7666 If present, this capability can be enabled for a VM, meaning that KVM
7679 maximum halt-polling time for all vCPUs in the target VM. This capability can
7694 This capability allows userspace to intercept RDMSR and WRMSR instructions if
7702 this capability. With it enabled, MSR accesses that match the mask specified in
7731 Enabling this capability on a VM provides userspace with a way to select
7747 This capability is aimed to address the thread that VM can exploit bus locks to
7749 capability and select the KVM_BUS_LOCK_DETECTION_EXIT mode, KVM will set the
7762 This capability can be used to check / enable 2nd DAWR feature provided
7774 This capability enables userspace to copy encryption context from the vm
7808 :Capability: KVM_CAP_PPC_RPT_INVALIDATE
7812 This capability indicates that the kernel is capable of handling
7820 This capability is enabled for hypervisors on platforms like POWER9
7829 When this capability is enabled, an emulation failure will result in an exit
7847 This capability indicates that KVM (and the hardware) supports exposing the
7850 available to a guest running in AArch64 mode and enabling this capability will
7858 When this capability is enabled all memory in memslots must be mapped as
7874 This capability enables userspace to migrate the encryption context from the VM
7883 :Capability: KVM_CAP_PPC_AIL_MODE_3
7887 This capability indicates that the kernel supports the mode 3 setting for the
7891 This capability allows a guest kernel to use a better-performance mode for
7897 :Capability: KVM_CAP_DISABLE_QUIRKS2
7902 This capability, if enabled, will cause KVM to disable some behavior
7905 Calling KVM_CHECK_EXTENSION for this capability returns a bitmask of
7908 The argument to KVM_ENABLE_CAP for this capability is a bitmask of
7975 This capability allows userspace to specify maximum possible APIC ID
8002 This capability allows userspace to configure the notify VM exit on/off
8012 This capability is aimed to mitigate the threat that malicious VMs can
8022 The presence of this capability indicates that KVM_RUN will fill
8048 This capability, if KVM_CHECK_EXTENSION indicates that it is
8052 with the KVM_CAP_PPC_ENABLE_HCALL capability.
8059 This capability, if KVM_CHECK_EXTENSION indicates that it is
8065 capability via KVM_ENABLE_CAP ioctl on the vcpu fd. Note that this
8074 This capability, if KVM_CHECK_EXTENSION indicates that it is
8084 This capability, if KVM_CHECK_EXTENSION indicates that it is
8094 This capability, if KVM_CHECK_EXTENSION on the main kvm handle indicates that
8100 If KVM_CHECK_EXTENSION on a kvm VM handle indicates that this capability is
8124 This capability, if KVM_CHECK_EXTENSION on the main kvm handle indicates that
8130 If KVM_CHECK_EXTENSION on a kvm VM handle indicates that this capability is
8138 This capability indicates the supported architecture type of the guest, i.e. the
8141 The values returned when this capability is checked by KVM_CHECK_EXTENSION on a
8166 This capability, if KVM_CHECK_EXTENSION indicates that it is available, means
8189 number larger than 0 indicating the version of this capability is implemented
8209 Querying this capability returns a bitmap indicating the possible
8219 This capability enables a newer version of Hyper-V Synthetic interrupt
8229 This capability indicates that userspace can load HV_X64_MSR_VP_INDEX msr. Its
8232 capability is absent, userspace can still query this msr's value.
8240 This capability indicates if the flic device will be able to get/set the
8249 This capability indicates that the PSW is exposed via the kvm_run structure.
8256 This capability indicates that the user space memory used as guest mapping can
8265 This capability indicates that the user space memory used as guest mapping can
8274 This capability indicates that kvm will implement the interfaces to handle
8276 facility 82 should not be provided to the guest without this capability.
8283 This capability indicates that KVM supports paravirtualized Hyper-V TLB Flush
8293 This capability indicates that userspace can specify (via the
8296 If KVM advertises this capability, userspace can only specify the ISS field for
8308 This capability indicates that KVM supports paravirtualized Hyper-V IPI send
8317 This capability indicates that KVM running on top of Hyper-V hypervisor
8321 KVM, enabling this capability effectively disables all hypercall
8332 This capability indicates that the KVM_S390_NORMAL_RESET and
8340 This capability indicates that the Ultravisor has been initialized and
8342 This capability governs the KVM_S390_PV_COMMAND ioctl and the
8351 This capability indicates that KVM supports steal time accounting.
8353 architecture-specific interfaces. This capability and the architecture-
8364 This capability enables a guest to set information about its control program
8376 If this capability is available, then the CPNC and CPVC can be synchronized
8384 This capability indicates that KVM supports deflection of MSR reads and
8395 This capability indicates that KVM supports that accesses to user defined MSRs
8396 may be rejected. With this capability exposed, KVM exports new VM ioctl
8440 ioctl to enable this capability for the new guest and set the size of
8441 the rings. Enabling the capability is only allowed before creating any
8499 NOTE: KVM_CAP_DIRTY_LOG_RING_ACQ_REL is the only capability that
8508 capability of KVM_CAP_DIRTY_LOG_RING_WITH_BITMAP to see whether the
8509 ring structures can be backed by per-slot bitmaps. With this capability
8513 can't be enabled if the capability of KVM_CAP_DIRTY_LOG_RING_ACQ_REL
8543 This capability indicates the features that Xen supports for hosting Xen
8605 :Capability: KVM_CAP_PPC_MULTITCE
8609 This capability means the kernel is capable of handling hypercalls
8626 This capability is always enabled.
8633 This capability indicates that the KVM virtual PTP service is
8651 :Capability: KVM_CAP_EXIT_HYPERCALL
8655 This capability, if enabled, will cause KVM to exit to userspace
8658 Calling KVM_CHECK_EXTENSION for this capability will return a bitmask
8670 :Capability: KVM_CAP_PMU_CAPABILITY
8676 This capability alters PMU virtualization in KVM.
8678 Calling KVM_CHECK_EXTENSION for this capability returns a bitmask of
8685 At this time, KVM_PMU_CAP_DISABLE is the only capability. Setting
8686 this capability will disable PMU virtualization for that VM. Usermode
8692 :Capability: KVM_CAP_ARM_SYSTEM_SUSPEND
8702 :Capability: KVM_CAP_S390_PROTECTED_DUMP
8706 This capability indicates that KVM and the Ultravisor support dumping
8715 :Capability: KVM_CAP_VM_DISABLE_NX_HUGE_PAGES
8723 This capability disables the NX huge pages mitigation for iTLB MULTIHIT.
8725 The capability has no effect if the nx_huge_pages module parameter is not set.
8727 This capability may only be set before any vCPUs are created.
8732 :Capability: KVM_CAP_S390_CPU_TOPOLOGY
8736 This capability indicates that KVM will provide the S390 CPU Topology
8743 to the guest without this capability.
8745 When this capability is present, KVM provides a new attribute group
8757 :Capability: KVM_CAP_ARM_EAGER_SPLIT_CHUNK_SIZE
8763 This capability sets the chunk size used in Eager Page Splitting.
8784 :Capability: KVM_CAP_MEMORY_ATTRIBUTES
8788 This capability returns a bitmap of support VM types. The 1-setting of bit @n