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
1415 :Capability: KVM_CAP_SET_TSS_ADDR
1435 :Capability: KVM_CAP_ENABLE_CAP
1441 :Capability: KVM_CAP_ENABLE_CAP_VM
1455 To check if a capability can be enabled, the KVM_CHECK_EXTENSION ioctl should
1464 The capability that is supposed to get enabled.
1490 :Capability: KVM_CAP_MP_STATE
1571 :Capability: KVM_CAP_MP_STATE
1596 :Capability: KVM_CAP_SET_IDENTITY_MAP_ADDR
1620 :Capability: KVM_CAP_SET_BOOT_CPU_ID
1635 :Capability: KVM_CAP_XSAVE
1655 :Capability: KVM_CAP_XSAVE and KVM_CAP_XSAVE2
1683 :Capability: KVM_CAP_XCRS
1710 :Capability: KVM_CAP_XCRS
1737 :Capability: KVM_CAP_EXT_CPUID
1826 :Capability: KVM_CAP_PPC_GET_PVINFO
1856 :Capability: KVM_CAP_IRQ_ROUTING
1906   KVM_CAP_MSI_DEVID capability advertises the requirement to provide
1907   the device ID.  If this capability is not available, userspace should
1933 feature of KVM_CAP_X2APIC_API capability is enabled.  If it is enabled,
1970 :Capability: KVM_CAP_TSC_CONTROL / KVM_CAP_VM_TSC_CONTROL
1979 If the KVM_CAP_VM_TSC_CONTROL capability is advertised, this can also
1986 :Capability: KVM_CAP_GET_TSC_KHZ / KVM_CAP_VM_TSC_CONTROL
2000 :Capability: KVM_CAP_IRQCHIP
2031 :Capability: KVM_CAP_IRQCHIP
2048 regs field) depends on the state of the KVM_CAP_X2APIC_API capability.
2055 :Capability: KVM_CAP_IOEVENTFD
2101 :Capability: KVM_CAP_SW_TLB
2137 :Capability: KVM_CAP_SPAPR_TCE
2146 and provides a scatter/gather capability for PAPR virtual I/O.
2176 :Capability: KVM_CAP_PPC_RMA
2203 The KVM_CAP_PPC_RMA capability is 1 or 2 if the KVM_ALLOCATE_RMA ioctl
2212 :Capability: KVM_CAP_USER_NMI
2239 :Capability: KVM_CAP_S390_UCONTROL
2261 :Capability: KVM_CAP_S390_UCONTROL
2283 :Capability: KVM_CAP_S390_UCONTROL
2301 :Capability: KVM_CAP_ONE_REG
2916 :Capability: KVM_CAP_ONE_REG
2946 :Capability: KVM_CAP_KVMCLOCK_CTRL
2970 :Capability: KVM_CAP_SIGNAL_MSI
2992   KVM_CAP_MSI_DEVID capability advertises the requirement to provide
2993   the device ID.  If this capability is not available, userspace
3001 feature of KVM_CAP_X2APIC_API capability is enabled.  If it is enabled,
3009 :Capability: KVM_CAP_PIT2
3042 :Capability: KVM_CAP_PIT_STATE2
3070 :Capability: KVM_CAP_PIT_STATE2
3085 :Capability: KVM_CAP_PPC_GET_SMMU_INFO
3160 :Capability: KVM_CAP_IRQFD
3199 :Capability: KVM_CAP_PPC_ALLOC_HTAB
3208 virtualization.  Otherwise the capability doesn't exist and the ioctl
3236 :Capability: basic
3291 :Capability: KVM_CAP_PPC_HTAB_FD
3346 :Capability: KVM_CAP_DEVICE_CTRL
3385 :Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device,
3422 :Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device,
3446 :Capability: basic
3544 :Capability: basic
3573 :Capability: basic
3600 :Capability: KVM_CAP_ARM_SET_DEVICE_ADDR
3649 :Capability: KVM_CAP_PPC_RTAS
3669 :Capability: KVM_CAP_SET_GUEST_DEBUG
3717 For ppc, the KVM_CAP_PPC_GUEST_DEBUG_SSTEP capability indicates whether
3720 Also when supported, KVM_CAP_SET_GUEST_DEBUG2 capability indicates the
3730 :Capability: KVM_CAP_EXT_EMUL_CPUID
3805 :Capability: KVM_CAP_S390_MEM_OP, KVM_CAP_S390_PROTECTED, KVM_CAP_S390_MEM_OP_EXTENSION
3814 The KVM_CAP_S390_MEM_OP_EXTENSION capability specifies what functionality is
3840 KVM_CAP_S390_MEM_OP capability. "buf" is the buffer supplied by the
3941 SIDA accesses are available if the KVM_CAP_S390_PROTECTED capability is available.
3950 :Capability: KVM_CAP_S390_SKEYS
3982 :Capability: KVM_CAP_S390_SKEYS
4010 :Capability: KVM_CAP_S390_INJECT_IRQ
4070 :Capability: KVM_CAP_S390_IRQ_STATE
4105 :Capability: KVM_CAP_S390_IRQ_STATE
4143 :Capability: KVM_CAP_X86_SMM
4154 :Capability: KVM_CAP_X86_MSR_FILTER
4267 :Capability: KVM_CAP_SPAPR_TCE_64
4276 This capability uses extended struct in ioctl interface::
4300 :Capability: KVM_CAP_REINJECT_CONTROL
4327 :Capability: KVM_CAP_PPC_MMU_RADIX or KVM_CAP_PPC_MMU_HASH_V3
4361 :Capability: KVM_CAP_PPC_MMU_RADIX
4398 :Capability: KVM_CAP_SPAPR_RESIZE_HPT
4452 :Capability: KVM_CAP_SPAPR_RESIZE_HPT
4497 :Capability: KVM_CAP_MCE
4510 :Capability: KVM_CAP_MCE
4517          -EINVAL if requested MCE capability is not supported.
4529 :Capability: KVM_CAP_MCE
4563 :Capability: KVM_CAP_S390_CMMA_MIGRATION
4664 :Capability: KVM_CAP_S390_CMMA_MIGRATION
4712 :Capability: KVM_CAP_PPC_GET_CPU_CHAR
4759 :Capability: basic
4776 :Capability: basic
4800 :Capability: basic
4812 :Capability: KVM_CAP_HYPERV_EVENTFD
4847 :Capability: KVM_CAP_NESTED_STATE
4921 :Capability: KVM_CAP_NESTED_STATE
4933 :Capability: KVM_CAP_COALESCED_MMIO (for coalesced mmio)
4962 :Capability: KVM_CAP_MANUAL_DIRTY_LOG_PROTECT2
4997 is enabled; for more information, see the description of the capability.
5004 :Capability: KVM_CAP_HYPERV_CPUID (vcpu), KVM_CAP_SYS_HYPERV_CPUID (system)
5117 :Capability: KVM_CAP_PMU_EVENT_FILTER
5164 :Capability: KVM_CAP_PMU_EVENT_MASKED_EVENTS
5233 :Capability: basic
5257 :Capability: KVM_CAP_S390_VCPU_RESETS
5269 :Capability: none
5282 :Capability: KVM_CAP_S390_VCPU_RESETS
5296 :Capability: KVM_CAP_S390_PROTECTED
5357   :Capability: KVM_CAP_S390_PROTECTED_DUMP
5422   :Capability: KVM_CAP_S390_PROTECTED_DUMP
5467   :Capability: KVM_CAP_S390_PROTECTED_ASYNC_DISABLE
5484   :Capability: KVM_CAP_S390_PROTECTED_ASYNC_DISABLE
5499 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5622 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5635 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5749 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5764 :Capability: KVM_CAP_ARM_MTE
5802 :Capability: KVM_CAP_SREGS2
5835 :Capability: KVM_CAP_SREGS2
5848 :Capability: KVM_CAP_STATS_BINARY_FD
6051 :Capability: KVM_CAP_XSAVE2
6078 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_EVTCHN_SEND
6098 :Capability: KVM_CAP_S390_PROTECTED_DUMP
6123 :Capability: KVM_CAP_S390_ZPCI_OP
6170 :Capability: KVM_CAP_COUNTER_OFFSET
6176 This capability indicates that userspace is able to apply a single VM-wide
6210 :Capability: KVM_CAP_ARM_SUPPORTED_REG_MASK_RANGES
6236 capability returns the supported ranges, expressed as a set of flags. Each
6258 :Capability: KVM_CAP_USER_MEMORY2
6309 :Capability: KVM_CAP_MEMORY_ATTRIBUTES
6345 :Capability: KVM_CAP_GUEST_MEMFD
6388 :Capability: KVM_CAP_PRE_FAULT_MEMORY
6441 the capability to be present.
6869 KVM_CAP_ARM_SYSTEM_SUSPEND VM capability. If a guest invokes the PSCI
6980 this capability at VM creation. Once this is done, these types of errors will
7009 Used on x86 systems. When the VM capability KVM_CAP_X86_USER_SPACE_MSR is
7120 Used on x86 systems. When the VM capability KVM_CAP_X86_NOTIFY_VMEXIT is
7180       whether this is a per-vcpu or per-vm capability.
7183       what parameters are accepted by the capability.
7198 This capability enables interception of OSI hypercalls that otherwise would
7203 When this capability is enabled, KVM_EXIT_OSI can occur.
7214 This capability enables interception of PAPR hypercalls. PAPR hypercalls are
7224 When this capability is enabled, KVM_EXIT_PAPR_HCALL can occur.
7282 This capability enables support for handling of channel I/O instructions.
7287 When this capability is enabled, KVM_EXIT_S390_TSCH will occur on TEST
7290 Note that even though this capability is enabled per-vcpu, the complete
7301 This capability enables or disables the delivery of interrupts through the
7310 When this capability is enabled, KVM_EXIT_EPR can occur.
7319 This capability connects the vcpu to an in-kernel MPIC device.
7329 This capability connects the vcpu to an in-kernel XICS device.
7338 This capability enables the in-kernel irqchip for s390. Please refer to
7348 This capability allows the use of the host Floating Point Unit by the guest. It
7362 This capability allows the use of the MIPS SIMD Architecture (MSA) by the guest.
7422 This capability connects the vcpu to an in-kernel XIVE device.
7439       what parameters are accepted by the capability.
7453 This capability controls whether individual sPAPR hypercalls (hcalls)
7458 before this capability was implemented.  If disabled, the kernel will
7474 This capability controls which SIGP orders will be handled completely in user
7475 space. With this capability enabled, all fast orders will be handled completely
7487 in the hardware prior to interception). If this capability is not enabled, the
7507 This capability allows post-handlers for the STSI instruction. After
7543 This capability also enables in kernel routing of interrupt requests;
7591 With this capability enabled, all illegal instructions 0x0000 (2 bytes) will
7597 This capability can be enabled dynamically even if VCPUs were already
7625 Enabling this capability on a VM provides userspace with a way to set
7630 be 0.  A successful call to enable this capability will result in
7631 vsmt_mode being returned when the KVM_CAP_PPC_SMT capability is
7632 subsequently queried for the VM.  This capability is only supported by
7634 The KVM_CAP_PPC_SMT_POSSIBLE capability indicates which virtual SMT
7643 With this capability a machine check exception in the guest address
7646 machine check handling routine. Without this capability KVM will
7663 Enabling this capability on a VM provides userspace with a way to no
7681 With this capability the KVM support for memory backing with 1m pages
7682 through hugetlbfs can be enabled for a VM. After the capability is
7688 this capability, the VM will not be able to run.
7696 With this capability, a guest may read the MSR_PLATFORM_INFO MSR. Otherwise,
7698 capability does not enable write permissions of this MSR for the guest.
7711 state).  Enabling this capability on a VM depends on the CPU having
7721 With this capability enabled, CR2 will not be modified prior to the
7733 This capability also enables exception.pending in struct
7788 This capability indicates that KVM is running on a host that has
7796 If present, this capability can be enabled for a VM, meaning that KVM
7809 maximum halt-polling time for all vCPUs in the target VM. This capability can
7824 This capability allows userspace to intercept RDMSR and WRMSR instructions if
7832 this capability. With it enabled, MSR accesses that match the mask specified in
7861 Enabling this capability on a VM provides userspace with a way to select a
7866 This capability allows userspace to force VM exits on bus locks detected in the
7868 (which triggers an #AC exception that KVM intercepts). This capability is
7894 This capability can be used to check / enable 2nd DAWR feature provided
7906 This capability enables userspace to copy encryption context from the vm
7940 :Capability: KVM_CAP_PPC_RPT_INVALIDATE
7944 This capability indicates that the kernel is capable of handling
7952 This capability is enabled for hypervisors on platforms like POWER9
7961 When this capability is enabled, an emulation failure will result in an exit
7979 This capability indicates that KVM (and the hardware) supports exposing the
7982 available to a guest running in AArch64 mode and enabling this capability will
7990 When this capability is enabled all memory in memslots must be mapped as
8006 This capability enables userspace to migrate the encryption context from the VM
8015 :Capability: KVM_CAP_PPC_AIL_MODE_3
8019 This capability indicates that the kernel supports the mode 3 setting for the
8023 This capability allows a guest kernel to use a better-performance mode for
8029 :Capability: KVM_CAP_DISABLE_QUIRKS2
8034 This capability, if enabled, will cause KVM to disable some behavior
8037 Calling KVM_CHECK_EXTENSION for this capability returns a bitmask of
8040 The argument to KVM_ENABLE_CAP for this capability is a bitmask of
8121 This capability allows userspace to specify maximum possible APIC ID
8148 This capability allows userspace to configure the notify VM exit on/off
8158 This capability is aimed to mitigate the threat that malicious VMs can
8168 The presence of this capability indicates that KVM_RUN will fill
8193 This capability sets the VM's APIC bus clock frequency, used by KVM's in-kernel
8206 The presence of this capability indicates that KVM_RUN will update the
8225 This capability, if KVM_CHECK_EXTENSION indicates that it is
8229 with the KVM_CAP_PPC_ENABLE_HCALL capability.
8236 This capability, if KVM_CHECK_EXTENSION indicates that it is
8242 capability via KVM_ENABLE_CAP ioctl on the vcpu fd. Note that this
8251 This capability, if KVM_CHECK_EXTENSION indicates that it is
8261 This capability, if KVM_CHECK_EXTENSION indicates that it is
8271 This capability, if KVM_CHECK_EXTENSION on the main kvm handle indicates that
8277 If KVM_CHECK_EXTENSION on a kvm VM handle indicates that this capability is
8301 This capability, if KVM_CHECK_EXTENSION on the main kvm handle indicates that
8307 If KVM_CHECK_EXTENSION on a kvm VM handle indicates that this capability is
8315 This capability indicates the supported architecture type of the guest, i.e. the
8318 The values returned when this capability is checked by KVM_CHECK_EXTENSION on a
8343 This capability, if KVM_CHECK_EXTENSION indicates that it is available, means
8366 number larger than 0 indicating the version of this capability is implemented
8386 Querying this capability returns a bitmap indicating the possible
8396 This capability enables a newer version of Hyper-V Synthetic interrupt
8406 This capability indicates that userspace can load HV_X64_MSR_VP_INDEX msr.  Its
8409 capability is absent, userspace can still query this msr's value.
8417 This capability indicates if the flic device will be able to get/set the
8426 This capability indicates that the PSW is exposed via the kvm_run structure.
8433 This capability indicates that the user space memory used as guest mapping can
8442 This capability indicates that the user space memory used as guest mapping can
8451 This capability indicates that kvm will implement the interfaces to handle
8453 facility 82 should not be provided to the guest without this capability.
8460 This capability indicates that KVM supports paravirtualized Hyper-V TLB Flush
8470 This capability indicates that userspace can specify (via the
8473 If KVM advertises this capability, userspace can only specify the ISS field for
8485 This capability indicates that KVM supports paravirtualized Hyper-V IPI send
8494 This capability indicates that KVM running on top of Hyper-V hypervisor
8498 KVM, enabling this capability effectively disables all hypercall
8509 This capability indicates that the KVM_S390_NORMAL_RESET and
8517 This capability indicates that the Ultravisor has been initialized and
8519 This capability governs the KVM_S390_PV_COMMAND ioctl and the
8528 This capability indicates that KVM supports steal time accounting.
8530 architecture-specific interfaces.  This capability and the architecture-
8541 This capability enables a guest to set information about its control program
8553 If this capability is available, then the CPNC and CPVC can be synchronized
8561 This capability indicates that KVM supports deflection of MSR reads and
8572 This capability indicates that KVM supports that accesses to user defined MSRs
8573 may be rejected. With this capability exposed, KVM exports new VM ioctl
8617 ioctl to enable this capability for the new guest and set the size of
8618 the rings.  Enabling the capability is only allowed before creating any
8676 NOTE: KVM_CAP_DIRTY_LOG_RING_ACQ_REL is the only capability that
8685 capability of KVM_CAP_DIRTY_LOG_RING_WITH_BITMAP to see whether the
8686 ring structures can be backed by per-slot bitmaps. With this capability
8690 can't be enabled if the capability of KVM_CAP_DIRTY_LOG_RING_ACQ_REL
8720 This capability indicates the features that Xen supports for hosting Xen
8782 :Capability: KVM_CAP_PPC_MULTITCE
8786 This capability means the kernel is capable of handling hypercalls
8803 This capability is always enabled.
8810 This capability indicates that the KVM virtual PTP service is
8828 :Capability: KVM_CAP_EXIT_HYPERCALL
8832 This capability, if enabled, will cause KVM to exit to userspace
8835 Calling KVM_CHECK_EXTENSION for this capability will return a bitmask
8847 :Capability: KVM_CAP_PMU_CAPABILITY
8853 This capability alters PMU virtualization in KVM.
8855 Calling KVM_CHECK_EXTENSION for this capability returns a bitmask of
8862 At this time, KVM_PMU_CAP_DISABLE is the only capability.  Setting
8863 this capability will disable PMU virtualization for that VM.  Usermode
8869 :Capability: KVM_CAP_ARM_SYSTEM_SUSPEND
8879 :Capability: KVM_CAP_S390_PROTECTED_DUMP
8883 This capability indicates that KVM and the Ultravisor support dumping
8892 :Capability: KVM_CAP_VM_DISABLE_NX_HUGE_PAGES
8900 This capability disables the NX huge pages mitigation for iTLB MULTIHIT.
8902 The capability has no effect if the nx_huge_pages module parameter is not set.
8904 This capability may only be set before any vCPUs are created.
8909 :Capability: KVM_CAP_S390_CPU_TOPOLOGY
8913 This capability indicates that KVM will provide the S390 CPU Topology
8920 to the guest without this capability.
8922 When this capability is present, KVM provides a new attribute group
8934 :Capability: KVM_CAP_ARM_EAGER_SPLIT_CHUNK_SIZE
8940 This capability sets the chunk size used in Eager Page Splitting.
8961 :Capability: KVM_CAP_MEMORY_ATTRIBUTES
8965 This capability returns a bitmap of support VM types.  The 1-setting of bit @n