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
1041 :Capability: KVM_CAP_ADJUST_CLOCK
1091 :Capability: KVM_CAP_ADJUST_CLOCK
1126 :Capability: KVM_CAP_VCPU_EVENTS
1252 :Capability: KVM_CAP_VCPU_EVENTS
1321 :Capability: KVM_CAP_DEBUGREGS
1343 :Capability: KVM_CAP_DEBUGREGS
1358 :Capability: KVM_CAP_USER_MEMORY
1387 KVM_CAP_MULTI_ADDRESS_SPACE capability. Slots in separate address spaces
1410 use it. The latter can be set, if KVM_CAP_READONLY_MEM capability allows it,
1414 When the KVM_CAP_SYNC_MMU capability is available, changes in the backing of
1440 :Capability: KVM_CAP_SET_TSS_ADDR
1462 :Capability: KVM_CAP_ENABLE_CAP
1468 :Capability: KVM_CAP_ENABLE_CAP_VM
1482 To check if a capability can be enabled, the KVM_CHECK_EXTENSION ioctl should
1491 The capability that is supposed to get enabled.
1517 :Capability: KVM_CAP_MP_STATE
1598 :Capability: KVM_CAP_MP_STATE
1623 :Capability: KVM_CAP_SET_IDENTITY_MAP_ADDR
1647 :Capability: KVM_CAP_SET_BOOT_CPU_ID
1662 :Capability: KVM_CAP_XSAVE
1682 :Capability: KVM_CAP_XSAVE and KVM_CAP_XSAVE2
1710 :Capability: KVM_CAP_XCRS
1737 :Capability: KVM_CAP_XCRS
1764 :Capability: KVM_CAP_EXT_CPUID
1856 :Capability: KVM_CAP_PPC_GET_PVINFO
1886 :Capability: KVM_CAP_IRQ_ROUTING
1939 KVM_CAP_MSI_DEVID capability advertises the requirement to provide
1940 the device ID. If this capability is not available, userspace should
1966 feature of KVM_CAP_X2APIC_API capability is enabled. If it is enabled,
2003 :Capability: KVM_CAP_TSC_CONTROL / KVM_CAP_VM_TSC_CONTROL
2012 If the KVM_CAP_VM_TSC_CONTROL capability is advertised, this can also
2026 :Capability: KVM_CAP_GET_TSC_KHZ / KVM_CAP_VM_TSC_CONTROL
2040 :Capability: KVM_CAP_IRQCHIP
2071 :Capability: KVM_CAP_IRQCHIP
2088 regs field) depends on the state of the KVM_CAP_X2APIC_API capability.
2095 :Capability: KVM_CAP_IOEVENTFD
2141 :Capability: KVM_CAP_SW_TLB
2177 :Capability: KVM_CAP_SPAPR_TCE
2186 and provides a scatter/gather capability for PAPR virtual I/O.
2216 :Capability: KVM_CAP_USER_NMI
2243 :Capability: KVM_CAP_S390_UCONTROL
2265 :Capability: KVM_CAP_S390_UCONTROL
2287 :Capability: KVM_CAP_S390_UCONTROL
2305 :Capability: KVM_CAP_ONE_REG
2930 :Capability: KVM_CAP_ONE_REG
2960 :Capability: KVM_CAP_KVMCLOCK_CTRL
2984 :Capability: KVM_CAP_SIGNAL_MSI
3006 KVM_CAP_MSI_DEVID capability advertises the requirement to provide
3007 the device ID. If this capability is not available, userspace
3015 feature of KVM_CAP_X2APIC_API capability is enabled. If it is enabled,
3023 :Capability: KVM_CAP_PIT2
3056 :Capability: KVM_CAP_PIT_STATE2
3084 :Capability: KVM_CAP_PIT_STATE2
3105 :Capability: KVM_CAP_PPC_GET_SMMU_INFO
3180 :Capability: KVM_CAP_IRQFD
3219 :Capability: KVM_CAP_PPC_ALLOC_HTAB
3228 virtualization. Otherwise the capability doesn't exist and the ioctl
3256 :Capability: basic
3311 :Capability: KVM_CAP_PPC_HTAB_FD
3366 :Capability: KVM_CAP_DEVICE_CTRL
3405 :Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device,
3442 :Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device,
3466 :Capability: basic
3576 :Capability: basic
3605 :Capability: basic
3655 :Capability: KVM_CAP_ARM_SET_DEVICE_ADDR
3704 :Capability: KVM_CAP_PPC_RTAS
3724 :Capability: KVM_CAP_SET_GUEST_DEBUG
3772 For ppc, the KVM_CAP_PPC_GUEST_DEBUG_SSTEP capability indicates whether
3775 Also when supported, KVM_CAP_SET_GUEST_DEBUG2 capability indicates the
3785 :Capability: KVM_CAP_EXT_EMUL_CPUID
3860 :Capability: KVM_CAP_S390_MEM_OP, KVM_CAP_S390_PROTECTED, KVM_CAP_S390_MEM_OP_EXTENSION
3869 The KVM_CAP_S390_MEM_OP_EXTENSION capability specifies what functionality is
3895 KVM_CAP_S390_MEM_OP capability. "buf" is the buffer supplied by the
3996 SIDA accesses are available if the KVM_CAP_S390_PROTECTED capability is available.
4005 :Capability: KVM_CAP_S390_SKEYS
4037 :Capability: KVM_CAP_S390_SKEYS
4065 :Capability: KVM_CAP_S390_INJECT_IRQ
4125 :Capability: KVM_CAP_S390_IRQ_STATE
4160 :Capability: KVM_CAP_S390_IRQ_STATE
4198 :Capability: KVM_CAP_X86_SMM
4209 :Capability: KVM_CAP_X86_MSR_FILTER
4322 :Capability: KVM_CAP_SPAPR_TCE_64
4331 This capability uses extended struct in ioctl interface::
4355 :Capability: KVM_CAP_REINJECT_CONTROL
4382 :Capability: KVM_CAP_PPC_MMU_RADIX or KVM_CAP_PPC_MMU_HASH_V3
4416 :Capability: KVM_CAP_PPC_MMU_RADIX
4453 :Capability: KVM_CAP_SPAPR_RESIZE_HPT
4507 :Capability: KVM_CAP_SPAPR_RESIZE_HPT
4552 :Capability: KVM_CAP_MCE
4565 :Capability: KVM_CAP_MCE
4572 -EINVAL if requested MCE capability is not supported.
4584 :Capability: KVM_CAP_MCE
4618 :Capability: KVM_CAP_S390_CMMA_MIGRATION
4719 :Capability: KVM_CAP_S390_CMMA_MIGRATION
4767 :Capability: KVM_CAP_PPC_GET_CPU_CHAR
4814 :Capability: basic
4833 :Capability: basic
4857 :Capability: basic
4869 :Capability: KVM_CAP_HYPERV_EVENTFD
4904 :Capability: KVM_CAP_NESTED_STATE
4978 :Capability: KVM_CAP_NESTED_STATE
4990 :Capability: KVM_CAP_COALESCED_MMIO (for coalesced mmio)
5019 :Capability: KVM_CAP_MANUAL_DIRTY_LOG_PROTECT2
5054 is enabled; for more information, see the description of the capability.
5061 :Capability: KVM_CAP_HYPERV_CPUID (vcpu), KVM_CAP_SYS_HYPERV_CPUID (system)
5174 :Capability: KVM_CAP_PMU_EVENT_FILTER
5221 :Capability: KVM_CAP_PMU_EVENT_MASKED_EVENTS
5290 :Capability: basic
5314 :Capability: KVM_CAP_S390_VCPU_RESETS
5326 :Capability: basic
5339 :Capability: KVM_CAP_S390_VCPU_RESETS
5353 :Capability: KVM_CAP_S390_PROTECTED
5414 :Capability: KVM_CAP_S390_PROTECTED_DUMP
5479 :Capability: KVM_CAP_S390_PROTECTED_DUMP
5524 :Capability: KVM_CAP_S390_PROTECTED_ASYNC_DISABLE
5541 :Capability: KVM_CAP_S390_PROTECTED_ASYNC_DISABLE
5556 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5679 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5692 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5806 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_SHARED_INFO
5821 :Capability: KVM_CAP_ARM_MTE
5859 :Capability: KVM_CAP_SREGS2
5892 :Capability: KVM_CAP_SREGS2
5905 :Capability: KVM_CAP_STATS_BINARY_FD
6108 :Capability: KVM_CAP_XSAVE2
6135 :Capability: KVM_CAP_XEN_HVM / KVM_XEN_HVM_CONFIG_EVTCHN_SEND
6155 :Capability: KVM_CAP_S390_PROTECTED_DUMP
6180 :Capability: KVM_CAP_S390_ZPCI_OP
6227 :Capability: KVM_CAP_COUNTER_OFFSET
6233 This capability indicates that userspace is able to apply a single VM-wide
6267 :Capability: KVM_CAP_ARM_SUPPORTED_REG_MASK_RANGES
6293 capability returns the supported ranges, expressed as a set of flags. Each
6315 :Capability: KVM_CAP_USER_MEMORY2
6366 :Capability: KVM_CAP_MEMORY_ATTRIBUTES
6402 :Capability: KVM_CAP_GUEST_MEMFD
6440 The capability KVM_CAP_GUEST_MEMFD_FLAGS enumerates the `flags` that can be
6463 :Capability: KVM_CAP_PRE_FAULT_MEMORY
6516 the capability to be present.
6957 KVM_CAP_ARM_SYSTEM_SUSPEND VM capability. If a guest invokes the PSCI
7074 this capability at VM creation. Once this is done, these types of errors will
7103 Used on x86 systems. When the VM capability KVM_CAP_X86_USER_SPACE_MSR is
7214 Used on x86 systems. When the VM capability KVM_CAP_X86_NOTIFY_VMEXIT is
7341 whether this is a per-vcpu or per-vm capability.
7344 what parameters are accepted by the capability.
7359 This capability enables interception of OSI hypercalls that otherwise would
7364 When this capability is enabled, KVM_EXIT_OSI can occur.
7375 This capability enables interception of PAPR hypercalls. PAPR hypercalls are
7385 When this capability is enabled, KVM_EXIT_PAPR_HCALL can occur.
7443 This capability enables support for handling of channel I/O instructions.
7448 When this capability is enabled, KVM_EXIT_S390_TSCH will occur on TEST
7451 Note that even though this capability is enabled per-vcpu, the complete
7462 This capability enables or disables the delivery of interrupts through the
7471 When this capability is enabled, KVM_EXIT_EPR can occur.
7480 This capability connects the vcpu to an in-kernel MPIC device.
7490 This capability connects the vcpu to an in-kernel XICS device.
7499 This capability enables the in-kernel irqchip for s390. Please refer to
7509 This capability allows the use of the host Floating Point Unit by the guest. It
7523 This capability allows the use of the MIPS SIMD Architecture (MSA) by the guest.
7583 This capability connects the vcpu to an in-kernel XIVE device.
7591 This capability, if KVM_CHECK_EXTENSION indicates that it is
7597 capability via KVM_ENABLE_CAP ioctl on the vcpu fd. Note that this
7607 This capability enables a newer version of Hyper-V Synthetic interrupt
7618 This capability indicates that KVM running on top of Hyper-V hypervisor
7622 KVM, enabling this capability effectively disables all hypercall
7671 what parameters are accepted by the capability.
7685 This capability controls whether individual sPAPR hypercalls (hcalls)
7690 before this capability was implemented. If disabled, the kernel will
7706 This capability controls which SIGP orders will be handled completely in user
7707 space. With this capability enabled, all fast orders will be handled completely
7719 in the hardware prior to interception). If this capability is not enabled, the
7739 This capability allows post-handlers for the STSI instruction. After
7775 This capability also enables in kernel routing of interrupt requests;
7823 With this capability enabled, all illegal instructions 0x0000 (2 bytes) will
7829 This capability can be enabled dynamically even if VCPUs were already
7857 Enabling this capability on a VM provides userspace with a way to set
7862 be 0. A successful call to enable this capability will result in
7863 vsmt_mode being returned when the KVM_CAP_PPC_SMT capability is
7864 subsequently queried for the VM. This capability is only supported by
7866 The KVM_CAP_PPC_SMT_POSSIBLE capability indicates which virtual SMT
7875 With this capability a machine check exception in the guest address
7878 machine check handling routine. Without this capability KVM will
7897 Enabling this capability on a VM provides userspace with a way to no
7922 passthrough capability with the guest CPUID bit,
7937 With this capability the KVM support for memory backing with 1m pages
7938 through hugetlbfs can be enabled for a VM. After the capability is
7944 this capability, the VM will not be able to run.
7952 With this capability, a guest may read the MSR_PLATFORM_INFO MSR. Otherwise,
7954 capability does not enable write permissions of this MSR for the guest.
7967 state). Enabling this capability on a VM depends on the CPU having
7977 With this capability enabled, CR2 will not be modified prior to the
7989 This capability also enables exception.pending in struct
8044 This capability indicates that KVM is running on a host that has
8052 If present, this capability can be enabled for a VM, meaning that KVM
8065 maximum halt-polling time for all vCPUs in the target VM. This capability can
8080 This capability allows userspace to intercept RDMSR and WRMSR instructions if
8088 this capability. With it enabled, MSR accesses that match the mask specified in
8117 Enabling this capability on a VM provides userspace with a way to select a
8122 This capability allows userspace to force VM exits on bus locks detected in the
8124 (which triggers an #AC exception that KVM intercepts). This capability is
8155 This capability can be used to check / enable 2nd DAWR feature provided
8167 This capability enables userspace to copy encryption context from the vm
8204 When this capability is enabled, an emulation failure will result in an exit
8222 This capability indicates that KVM (and the hardware) supports exposing the
8225 available to a guest running in AArch64 mode and enabling this capability will
8233 When this capability is enabled all memory in memslots must be mapped as
8249 This capability enables userspace to migrate the encryption context from the VM
8262 This capability, if enabled, will cause KVM to disable some behavior
8265 Calling KVM_CHECK_EXTENSION for this capability returns a bitmask of
8268 The argument to KVM_ENABLE_CAP for this capability is a bitmask of
8393 This capability allows userspace to specify maximum possible APIC ID
8420 This capability allows userspace to configure the notify VM exit on/off
8430 This capability is aimed to mitigate the threat that malicious VMs can
8444 This capability sets the VM's APIC bus clock frequency, used by KVM's in-kernel
8478 ioctl to enable this capability for the new guest and set the size of
8479 the rings. Enabling the capability is only allowed before creating any
8537 NOTE: KVM_CAP_DIRTY_LOG_RING_ACQ_REL is the only capability that
8546 capability of KVM_CAP_DIRTY_LOG_RING_WITH_BITMAP to see whether the
8547 ring structures can be backed by per-slot bitmaps. With this capability
8551 can't be enabled if the capability of KVM_CAP_DIRTY_LOG_RING_ACQ_REL
8584 This capability alters PMU virtualization in KVM.
8586 Calling KVM_CHECK_EXTENSION for this capability returns a bitmask of
8593 At this time, KVM_PMU_CAP_DISABLE is the only capability. Setting
8594 this capability will disable PMU virtualization for that VM. Usermode
8607 This capability disables the NX huge pages mitigation for iTLB MULTIHIT.
8609 The capability has no effect if the nx_huge_pages module parameter is not set.
8611 This capability may only be set before any vCPUs are created.
8621 This capability sets the chunk size used in Eager Page Splitting.
8645 This capability, if enabled, will cause KVM to exit to userspace
8648 Calling KVM_CHECK_EXTENSION for this capability will return a bitmask
8673 capability.
8675 This capability changes the behavior of the registers that identify a PE
8679 When this capability is enabled, KVM allows userspace to change the
8692 When this capability is enabled, KVM resets the VCPU when setting
8702 This capability indicate to the userspace whether a PFNMAP memory region
8717 This capability, if KVM_CHECK_EXTENSION indicates that it is
8721 with the KVM_CAP_PPC_ENABLE_HCALL capability.
8728 This capability, if KVM_CHECK_EXTENSION indicates that it is
8738 This capability, if KVM_CHECK_EXTENSION indicates that it is
8748 This capability, if KVM_CHECK_EXTENSION on the main kvm handle indicates that
8754 If KVM_CHECK_EXTENSION on a kvm VM handle indicates that this capability is
8778 This capability indicates the supported architecture type of the guest, i.e. the
8781 The values returned when this capability is checked by KVM_CHECK_EXTENSION on a
8806 This capability, if KVM_CHECK_EXTENSION indicates that it is available, means
8829 number larger than 0 indicating the version of this capability is implemented
8849 Querying this capability returns a bitmap indicating the possible
8859 This capability indicates that userspace can load HV_X64_MSR_VP_INDEX msr. Its
8862 capability is absent, userspace can still query this msr's value.
8869 This capability indicates if the flic device will be able to get/set the
8878 This capability indicates that the PSW is exposed via the kvm_run structure.
8885 This capability indicates that the user space memory used as guest mapping can
8894 This capability indicates that the user space memory used as guest mapping can
8903 This capability indicates that kvm will implement the interfaces to handle
8905 facility 82 should not be provided to the guest without this capability.
8912 This capability indicates that KVM supports paravirtualized Hyper-V TLB Flush
8922 This capability indicates that userspace can specify (via the
8925 If KVM advertises this capability, userspace can only specify the ISS field for
8937 This capability indicates that KVM supports paravirtualized Hyper-V IPI send
8946 This capability indicates that the KVM_S390_NORMAL_RESET and
8954 This capability indicates that the Ultravisor has been initialized and
8956 This capability governs the KVM_S390_PV_COMMAND ioctl and the
8965 This capability indicates that KVM supports steal time accounting.
8967 architecture-specific interfaces. This capability and the architecture-
8978 This capability enables a guest to set information about its control program
8990 If this capability is available, then the CPNC and CPVC can be synchronized
8998 This capability indicates that KVM supports deflection of MSR reads and
9009 This capability indicates that KVM supports that accesses to user defined MSRs
9010 may be rejected. With this capability exposed, KVM exports new VM ioctl
9023 This capability indicates the features that Xen supports for hosting Xen
9088 This capability means the kernel is capable of handling hypercalls
9105 This capability is always enabled.
9112 This capability indicates that the KVM virtual PTP service is
9122 This capability indicates that KVM and the Ultravisor support dumping
9134 This capability indicates that KVM will provide the S390 CPU Topology
9141 to the guest without this capability.
9143 When this capability is present, KVM provides a new attribute group
9158 This capability returns a bitmap of support VM types. The 1-setting of bit @n
9176 This capability indicates that the kernel is capable of handling
9184 This capability is enabled for hypervisors on platforms like POWER9
9192 This capability indicates that the kernel supports the mode 3 setting for the
9196 This capability allows a guest kernel to use a better-performance mode for
9204 The presence of this capability indicates that KVM_RUN will fill
9224 The presence of this capability indicates that KVM_RUN will update the