Lines Matching full:capability
108 Capability:
135 :Capability: basic
152 :Capability: basic
205 is dependent on the CPU capability and the kernel configuration. The limit can
212 Please note that configuring the IPA size does not affect the capability
221 :Capability: basic, KVM_CAP_GET_MSR_FEATURES for KVM_GET_MSR_FEATURE_INDEX_LIST
265 :Capability: basic, KVM_CAP_CHECK_EXTENSION_VM for vm ioctl
284 :Capability: basic
310 :Capability: basic
338 same partition.) The KVM_CAP_PPC_SMT capability indicates the number
357 :Capability: basic
386 see the description of the capability.
395 :Capability: basic
422 :Capability: basic
462 :Capability: basic
476 :Capability: basic
507 :Capability: basic
520 :Capability: basic
547 :Capability: basic
646 :Capability: basic (vcpu), KVM_CAP_GET_MSR_FEATURES (system)
686 :Capability: basic
708 :Capability: basic
748 :Capability: basic
774 :Capability: basic
812 :Capability: basic
850 :Capability: KVM_CAP_IRQCHIP, KVM_CAP_S390_IRQCHIP (s390)
865 Note that on s390 the KVM_CAP_S390_IRQCHIP vm capability needs to be enabled
872 :Capability: KVM_CAP_IRQCHIP
893 capability is present (or unless it is not using the in-kernel irqchip,
923 Note that on arm64, the KVM_CAP_IRQCHIP capability only conditions
941 :Capability: KVM_CAP_IRQCHIP
966 :Capability: KVM_CAP_IRQCHIP
991 :Capability: KVM_CAP_XEN_HVM
1037 :Capability: KVM_CAP_ADJUST_CLOCK
1087 :Capability: KVM_CAP_ADJUST_CLOCK
1122 :Capability: KVM_CAP_VCPU_EVENTS
1245 :Capability: KVM_CAP_VCPU_EVENTS
1312 :Capability: KVM_CAP_DEBUGREGS
1334 :Capability: KVM_CAP_DEBUGREGS
1349 :Capability: KVM_CAP_USER_MEMORY
1378 KVM_CAP_MULTI_ADDRESS_SPACE capability. Slots in separate address spaces
1401 use it. The latter can be set, if KVM_CAP_READONLY_MEM capability allows it,
1405 When the KVM_CAP_SYNC_MMU capability is available, changes in the backing of
1428 :Capability: KVM_CAP_SET_TSS_ADDR
1450 :Capability: KVM_CAP_ENABLE_CAP
1456 :Capability: KVM_CAP_ENABLE_CAP_VM
1470 To check if a capability can be enabled, the KVM_CHECK_EXTENSION ioctl should
1479 The capability that is supposed to get enabled.
1505 :Capability: KVM_CAP_MP_STATE
1586 :Capability: KVM_CAP_MP_STATE
1611 :Capability: KVM_CAP_SET_IDENTITY_MAP_ADDR
1635 :Capability: KVM_CAP_SET_BOOT_CPU_ID
1650 :Capability: KVM_CAP_XSAVE
1670 :Capability: KVM_CAP_XSAVE and KVM_CAP_XSAVE2
1698 :Capability: KVM_CAP_XCRS
1725 :Capability: KVM_CAP_XCRS
1752 :Capability: KVM_CAP_EXT_CPUID
1844 :Capability: KVM_CAP_PPC_GET_PVINFO
1874 :Capability: KVM_CAP_IRQ_ROUTING
1927 KVM_CAP_MSI_DEVID capability advertises the requirement to provide
1928 the device ID. If this capability is not available, userspace should
1954 feature of KVM_CAP_X2APIC_API capability is enabled. If it is enabled,
1991 :Capability: KVM_CAP_TSC_CONTROL / KVM_CAP_VM_TSC_CONTROL
2000 If the KVM_CAP_VM_TSC_CONTROL capability is advertised, this can also
2007 :Capability: KVM_CAP_GET_TSC_KHZ / KVM_CAP_VM_TSC_CONTROL
2021 :Capability: KVM_CAP_IRQCHIP
2052 :Capability: KVM_CAP_IRQCHIP
2069 regs field) depends on the state of the KVM_CAP_X2APIC_API capability.
2076 :Capability: KVM_CAP_IOEVENTFD
2122 :Capability: KVM_CAP_SW_TLB
2158 :Capability: KVM_CAP_SPAPR_TCE
2167 and provides a scatter/gather capability for PAPR virtual I/O.
2197 :Capability: KVM_CAP_USER_NMI
2224 :Capability: KVM_CAP_S390_UCONTROL
2246 :Capability: KVM_CAP_S390_UCONTROL
2268 :Capability: KVM_CAP_S390_UCONTROL
2286 :Capability: KVM_CAP_ONE_REG
2901 :Capability: KVM_CAP_ONE_REG
2931 :Capability: KVM_CAP_KVMCLOCK_CTRL
2955 :Capability: KVM_CAP_SIGNAL_MSI
2977 KVM_CAP_MSI_DEVID capability advertises the requirement to provide
2978 the device ID. If this capability is not available, userspace
2986 feature of KVM_CAP_X2APIC_API capability is enabled. If it is enabled,
2994 :Capability: KVM_CAP_PIT2
3027 :Capability: KVM_CAP_PIT_STATE2
3055 :Capability: KVM_CAP_PIT_STATE2
3070 :Capability: KVM_CAP_PPC_GET_SMMU_INFO
3145 :Capability: KVM_CAP_IRQFD
3184 :Capability: KVM_CAP_PPC_ALLOC_HTAB
3193 virtualization. Otherwise the capability doesn't exist and the ioctl
3221 :Capability: basic
3276 :Capability: KVM_CAP_PPC_HTAB_FD
3331 :Capability: KVM_CAP_DEVICE_CTRL
3370 :Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device,
3407 :Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device,
3431 :Capability: basic
3529 :Capability: basic
3558 :Capability: basic
3606 :Capability: KVM_CAP_ARM_SET_DEVICE_ADDR
3655 :Capability: KVM_CAP_PPC_RTAS
3675 :Capability: KVM_CAP_SET_GUEST_DEBUG
3723 For ppc, the KVM_CAP_PPC_GUEST_DEBUG_SSTEP capability indicates whether
3726 Also when supported, KVM_CAP_SET_GUEST_DEBUG2 capability indicates the
3736 :Capability: KVM_CAP_EXT_EMUL_CPUID
3811 :Capability: KVM_CAP_S390_MEM_OP, KVM_CAP_S390_PROTECTED, KVM_CAP_S390_MEM_OP_EXTENSION
3820 The KVM_CAP_S390_MEM_OP_EXTENSION capability specifies what functionality is
3846 KVM_CAP_S390_MEM_OP capability. "buf" is the buffer supplied by the
3947 SIDA accesses are available if the KVM_CAP_S390_PROTECTED capability is available.
3956 :Capability: KVM_CAP_S390_SKEYS
3988 :Capability: KVM_CAP_S390_SKEYS
4016 :Capability: KVM_CAP_S390_INJECT_IRQ
4076 :Capability: KVM_CAP_S390_IRQ_STATE
4111 :Capability: KVM_CAP_S390_IRQ_STATE
4149 :Capability: KVM_CAP_X86_SMM
4160 :Capability: KVM_CAP_X86_MSR_FILTER
4273 :Capability: KVM_CAP_SPAPR_TCE_64
4282 This capability uses extended struct in ioctl interface::
4306 :Capability: KVM_CAP_REINJECT_CONTROL
4333 :Capability: KVM_CAP_PPC_MMU_RADIX or KVM_CAP_PPC_MMU_HASH_V3
4367 :Capability: KVM_CAP_PPC_MMU_RADIX
4404 :Capability: KVM_CAP_SPAPR_RESIZE_HPT
4458 :Capability: KVM_CAP_SPAPR_RESIZE_HPT
4503 :Capability: KVM_CAP_MCE
4516 :Capability: KVM_CAP_MCE
4523 -EINVAL if requested MCE capability is not supported.
4535 :Capability: KVM_CAP_MCE
4569 :Capability: KVM_CAP_S390_CMMA_MIGRATION
4670 :Capability: KVM_CAP_S390_CMMA_MIGRATION
4718 :Capability: KVM_CAP_PPC_GET_CPU_CHAR
4765 :Capability: basic
4782 :Capability: basic
4806 :Capability: basic
4818 :Capability: KVM_CAP_HYPERV_EVENTFD
4853 :Capability: KVM_CAP_NESTED_STATE
4927 :Capability: KVM_CAP_NESTED_STATE
4939 :Capability: KVM_CAP_COALESCED_MMIO (for coalesced mmio)
4968 :Capability: KVM_CAP_MANUAL_DIRTY_LOG_PROTECT2
5003 is enabled; for more information, see the description of the capability.
5010 :Capability: KVM_CAP_HYPERV_CPUID (vcpu), KVM_CAP_SYS_HYPERV_CPUID (system)
5123 :Capability: KVM_CAP_PMU_EVENT_FILTER
5170 :Capability: KVM_CAP_PMU_EVENT_MASKED_EVENTS
5239 :Capability: basic
5263 :Capability: KVM_CAP_S390_VCPU_RESETS
5275 :Capability: basic
5288 :Capability: KVM_CAP_S390_VCPU_RESETS
5302 :Capability: KVM_CAP_S390_PROTECTED
5363 :Capability: KVM_CAP_S390_PROTECTED_DUMP
5428 :Capability: KVM_CAP_S390_PROTECTED_DUMP
5473 :Capability: KVM_CAP_S390_PROTECTED_ASYNC_DISABLE
5490 :Capability: KVM_CAP_S390_PROTECTED_ASYNC_DISABLE
5505 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5628 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5641 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5755 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5770 :Capability: KVM_CAP_ARM_MTE
5808 :Capability: KVM_CAP_SREGS2
5841 :Capability: KVM_CAP_SREGS2
5854 :Capability: KVM_CAP_STATS_BINARY_FD
6057 :Capability: KVM_CAP_XSAVE2
6084 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_EVTCHN_SEND
6104 :Capability: KVM_CAP_S390_PROTECTED_DUMP
6129 :Capability: KVM_CAP_S390_ZPCI_OP
6176 :Capability: KVM_CAP_COUNTER_OFFSET
6182 This capability indicates that userspace is able to apply a single VM-wide
6216 :Capability: KVM_CAP_ARM_SUPPORTED_REG_MASK_RANGES
6242 capability returns the supported ranges, expressed as a set of flags. Each
6264 :Capability: KVM_CAP_USER_MEMORY2
6315 :Capability: KVM_CAP_MEMORY_ATTRIBUTES
6351 :Capability: KVM_CAP_GUEST_MEMFD
6394 :Capability: KVM_CAP_PRE_FAULT_MEMORY
6447 the capability to be present.
6881 KVM_CAP_ARM_SYSTEM_SUSPEND VM capability. If a guest invokes the PSCI
6998 this capability at VM creation. Once this is done, these types of errors will
7027 Used on x86 systems. When the VM capability KVM_CAP_X86_USER_SPACE_MSR is
7138 Used on x86 systems. When the VM capability KVM_CAP_X86_NOTIFY_VMEXIT is
7202 whether this is a per-vcpu or per-vm capability.
7205 what parameters are accepted by the capability.
7220 This capability enables interception of OSI hypercalls that otherwise would
7225 When this capability is enabled, KVM_EXIT_OSI can occur.
7236 This capability enables interception of PAPR hypercalls. PAPR hypercalls are
7246 When this capability is enabled, KVM_EXIT_PAPR_HCALL can occur.
7304 This capability enables support for handling of channel I/O instructions.
7309 When this capability is enabled, KVM_EXIT_S390_TSCH will occur on TEST
7312 Note that even though this capability is enabled per-vcpu, the complete
7323 This capability enables or disables the delivery of interrupts through the
7332 When this capability is enabled, KVM_EXIT_EPR can occur.
7341 This capability connects the vcpu to an in-kernel MPIC device.
7351 This capability connects the vcpu to an in-kernel XICS device.
7360 This capability enables the in-kernel irqchip for s390. Please refer to
7370 This capability allows the use of the host Floating Point Unit by the guest. It
7384 This capability allows the use of the MIPS SIMD Architecture (MSA) by the guest.
7444 This capability connects the vcpu to an in-kernel XIVE device.
7463 what parameters are accepted by the capability.
7477 This capability controls whether individual sPAPR hypercalls (hcalls)
7482 before this capability was implemented. If disabled, the kernel will
7498 This capability controls which SIGP orders will be handled completely in user
7499 space. With this capability enabled, all fast orders will be handled completely
7511 in the hardware prior to interception). If this capability is not enabled, the
7531 This capability allows post-handlers for the STSI instruction. After
7567 This capability also enables in kernel routing of interrupt requests;
7615 With this capability enabled, all illegal instructions 0x0000 (2 bytes) will
7621 This capability can be enabled dynamically even if VCPUs were already
7649 Enabling this capability on a VM provides userspace with a way to set
7654 be 0. A successful call to enable this capability will result in
7655 vsmt_mode being returned when the KVM_CAP_PPC_SMT capability is
7656 subsequently queried for the VM. This capability is only supported by
7658 The KVM_CAP_PPC_SMT_POSSIBLE capability indicates which virtual SMT
7667 With this capability a machine check exception in the guest address
7670 machine check handling routine. Without this capability KVM will
7688 Enabling this capability on a VM provides userspace with a way to no
7706 With this capability the KVM support for memory backing with 1m pages
7707 through hugetlbfs can be enabled for a VM. After the capability is
7713 this capability, the VM will not be able to run.
7721 With this capability, a guest may read the MSR_PLATFORM_INFO MSR. Otherwise,
7723 capability does not enable write permissions of this MSR for the guest.
7736 state). Enabling this capability on a VM depends on the CPU having
7746 With this capability enabled, CR2 will not be modified prior to the
7758 This capability also enables exception.pending in struct
7813 This capability indicates that KVM is running on a host that has
7821 If present, this capability can be enabled for a VM, meaning that KVM
7834 maximum halt-polling time for all vCPUs in the target VM. This capability can
7849 This capability allows userspace to intercept RDMSR and WRMSR instructions if
7857 this capability. With it enabled, MSR accesses that match the mask specified in
7886 Enabling this capability on a VM provides userspace with a way to select a
7891 This capability allows userspace to force VM exits on bus locks detected in the
7893 (which triggers an #AC exception that KVM intercepts). This capability is
7919 This capability can be used to check / enable 2nd DAWR feature provided
7931 This capability enables userspace to copy encryption context from the vm
7965 :Capability: KVM_CAP_PPC_RPT_INVALIDATE
7969 This capability indicates that the kernel is capable of handling
7977 This capability is enabled for hypervisors on platforms like POWER9
7986 When this capability is enabled, an emulation failure will result in an exit
8004 This capability indicates that KVM (and the hardware) supports exposing the
8007 available to a guest running in AArch64 mode and enabling this capability will
8015 When this capability is enabled all memory in memslots must be mapped as
8031 This capability enables userspace to migrate the encryption context from the VM
8040 :Capability: KVM_CAP_PPC_AIL_MODE_3
8044 This capability indicates that the kernel supports the mode 3 setting for the
8048 This capability allows a guest kernel to use a better-performance mode for
8054 :Capability: KVM_CAP_DISABLE_QUIRKS2
8059 This capability, if enabled, will cause KVM to disable some behavior
8062 Calling KVM_CHECK_EXTENSION for this capability returns a bitmask of
8065 The argument to KVM_ENABLE_CAP for this capability is a bitmask of
8168 This capability allows userspace to specify maximum possible APIC ID
8195 This capability allows userspace to configure the notify VM exit on/off
8205 This capability is aimed to mitigate the threat that malicious VMs can
8215 The presence of this capability indicates that KVM_RUN will fill
8240 This capability sets the VM's APIC bus clock frequency, used by KVM's in-kernel
8253 The presence of this capability indicates that KVM_RUN will update the
8272 This capability, if KVM_CHECK_EXTENSION indicates that it is
8276 with the KVM_CAP_PPC_ENABLE_HCALL capability.
8283 This capability, if KVM_CHECK_EXTENSION indicates that it is
8289 capability via KVM_ENABLE_CAP ioctl on the vcpu fd. Note that this
8298 This capability, if KVM_CHECK_EXTENSION indicates that it is
8308 This capability, if KVM_CHECK_EXTENSION indicates that it is
8318 This capability, if KVM_CHECK_EXTENSION on the main kvm handle indicates that
8324 If KVM_CHECK_EXTENSION on a kvm VM handle indicates that this capability is
8348 This capability, if KVM_CHECK_EXTENSION on the main kvm handle indicates that
8354 If KVM_CHECK_EXTENSION on a kvm VM handle indicates that this capability is
8362 This capability indicates the supported architecture type of the guest, i.e. the
8365 The values returned when this capability is checked by KVM_CHECK_EXTENSION on a
8390 This capability, if KVM_CHECK_EXTENSION indicates that it is available, means
8413 number larger than 0 indicating the version of this capability is implemented
8433 Querying this capability returns a bitmap indicating the possible
8443 This capability enables a newer version of Hyper-V Synthetic interrupt
8453 This capability indicates that userspace can load HV_X64_MSR_VP_INDEX msr. Its
8456 capability is absent, userspace can still query this msr's value.
8464 This capability indicates if the flic device will be able to get/set the
8473 This capability indicates that the PSW is exposed via the kvm_run structure.
8480 This capability indicates that the user space memory used as guest mapping can
8489 This capability indicates that the user space memory used as guest mapping can
8498 This capability indicates that kvm will implement the interfaces to handle
8500 facility 82 should not be provided to the guest without this capability.
8507 This capability indicates that KVM supports paravirtualized Hyper-V TLB Flush
8517 This capability indicates that userspace can specify (via the
8520 If KVM advertises this capability, userspace can only specify the ISS field for
8532 This capability indicates that KVM supports paravirtualized Hyper-V IPI send
8541 This capability indicates that KVM running on top of Hyper-V hypervisor
8545 KVM, enabling this capability effectively disables all hypercall
8556 This capability indicates that the KVM_S390_NORMAL_RESET and
8564 This capability indicates that the Ultravisor has been initialized and
8566 This capability governs the KVM_S390_PV_COMMAND ioctl and the
8575 This capability indicates that KVM supports steal time accounting.
8577 architecture-specific interfaces. This capability and the architecture-
8588 This capability enables a guest to set information about its control program
8600 If this capability is available, then the CPNC and CPVC can be synchronized
8608 This capability indicates that KVM supports deflection of MSR reads and
8619 This capability indicates that KVM supports that accesses to user defined MSRs
8620 may be rejected. With this capability exposed, KVM exports new VM ioctl
8666 ioctl to enable this capability for the new guest and set the size of
8667 the rings. Enabling the capability is only allowed before creating any
8725 NOTE: KVM_CAP_DIRTY_LOG_RING_ACQ_REL is the only capability that
8734 capability of KVM_CAP_DIRTY_LOG_RING_WITH_BITMAP to see whether the
8735 ring structures can be backed by per-slot bitmaps. With this capability
8739 can't be enabled if the capability of KVM_CAP_DIRTY_LOG_RING_ACQ_REL
8769 This capability indicates the features that Xen supports for hosting Xen
8831 :Capability: KVM_CAP_PPC_MULTITCE
8835 This capability means the kernel is capable of handling hypercalls
8852 This capability is always enabled.
8859 This capability indicates that the KVM virtual PTP service is
8877 :Capability: KVM_CAP_EXIT_HYPERCALL
8881 This capability, if enabled, will cause KVM to exit to userspace
8884 Calling KVM_CHECK_EXTENSION for this capability will return a bitmask
8896 :Capability: KVM_CAP_PMU_CAPABILITY
8902 This capability alters PMU virtualization in KVM.
8904 Calling KVM_CHECK_EXTENSION for this capability returns a bitmask of
8911 At this time, KVM_PMU_CAP_DISABLE is the only capability. Setting
8912 this capability will disable PMU virtualization for that VM. Usermode
8918 :Capability: KVM_CAP_ARM_SYSTEM_SUSPEND
8928 :Capability: KVM_CAP_S390_PROTECTED_DUMP
8932 This capability indicates that KVM and the Ultravisor support dumping
8941 :Capability: KVM_CAP_VM_DISABLE_NX_HUGE_PAGES
8949 This capability disables the NX huge pages mitigation for iTLB MULTIHIT.
8951 The capability has no effect if the nx_huge_pages module parameter is not set.
8953 This capability may only be set before any vCPUs are created.
8958 :Capability: KVM_CAP_S390_CPU_TOPOLOGY
8962 This capability indicates that KVM will provide the S390 CPU Topology
8969 to the guest without this capability.
8971 When this capability is present, KVM provides a new attribute group
8983 :Capability: KVM_CAP_ARM_EAGER_SPLIT_CHUNK_SIZE
8989 This capability sets the chunk size used in Eager Page Splitting.
9010 :Capability: KVM_CAP_MEMORY_ATTRIBUTES
9014 This capability returns a bitmap of support VM types. The 1-setting of bit @n