Lines Matching full:capability
93 Capability: which KVM extension provides this ioctl. Can be 'basic',
98 support this ioctl, there's no capability bit to check its
115 Capability: basic
131 Capability: basic
171 is dependent on the CPU capability and the kernel configuration. The limit can
175 Please note that configuring the IPA size does not affect the capability
183 Capability: basic, KVM_CAP_GET_MSR_FEATURES for KVM_GET_MSR_FEATURE_INDEX_LIST
218 Capability: basic, KVM_CAP_CHECK_EXTENSION_VM for vm ioctl
236 Capability: basic
249 Capability: basic
260 Capability: basic
288 same partition.) The KVM_CAP_PPC_SMT capability indicates the number
306 Capability: basic
330 the KVM_CAP_MULTI_ADDRESS_SPACE capability.
334 see the description of the capability.
338 Capability: basic
349 Capability: basic
366 Capability: basic
396 Capability: basic
409 Capability: basic
437 Capability: basic
449 Capability: basic
473 Capability: basic
537 Capability: basic
548 Capability: basic (vcpu), KVM_CAP_GET_MSR_FEATURES (system)
585 Capability: basic
606 Capability: basic
635 Capability: basic
658 Capability: basic
684 Capability: basic
710 Capability: KVM_CAP_IRQCHIP, KVM_CAP_S390_IRQCHIP (s390)
725 Note that on s390 the KVM_CAP_S390_IRQCHIP vm capability needs to be enabled
731 Capability: KVM_CAP_IRQCHIP
752 capability is present (or unless it is not using the in-kernel irqchip,
778 Note that on arm/arm64, the KVM_CAP_IRQCHIP capability only conditions
793 Capability: KVM_CAP_IRQCHIP
815 Capability: KVM_CAP_IRQCHIP
837 Capability: KVM_CAP_XEN_HVM
862 Capability: KVM_CAP_ADJUST_CLOCK
892 Capability: KVM_CAP_ADJUST_CLOCK
911 Capability: KVM_CAP_VCPU_EVENTS
1018 Capability: KVM_CAP_VCPU_EVENTS
1062 Capability: KVM_CAP_DEBUGREGS
1081 Capability: KVM_CAP_DEBUGREGS
1095 Capability: KVM_CAP_USER_MEMORY
1122 KVM_CAP_MULTI_ADDRESS_SPACE capability. Slots in separate address spaces
1142 use it. The latter can be set, if KVM_CAP_READONLY_MEM capability allows it,
1146 When the KVM_CAP_SYNC_MMU capability is available, changes in the backing of
1158 Capability: KVM_CAP_SET_TSS_ADDR
1177 Capability: KVM_CAP_ENABLE_CAP
1183 Capability: KVM_CAP_ENABLE_CAP_VM
1195 To check if a capability can be enabled, the KVM_CHECK_EXTENSION ioctl should
1202 The capability that is supposed to get enabled.
1221 Capability: KVM_CAP_MP_STATE
1263 Capability: KVM_CAP_MP_STATE
1283 Capability: KVM_CAP_SET_IDENTITY_MAP_ADDR
1306 Capability: KVM_CAP_SET_BOOT_CPU_ID
1319 Capability: KVM_CAP_XSAVE
1334 Capability: KVM_CAP_XSAVE
1349 Capability: KVM_CAP_XCRS
1373 Capability: KVM_CAP_XCRS
1397 Capability: KVM_CAP_EXT_CPUID
1478 Capability: KVM_CAP_PPC_GET_PVINFO
1505 Capability: KVM_CAP_IRQ_ROUTING
1547 KVM_CAP_MSI_DEVID capability advertises the requirement to provide
1548 the device ID. If this capability is not available, userspace should
1572 feature of KVM_CAP_X2APIC_API capability is enabled. If it is enabled,
1592 Capability: KVM_CAP_TSC_CONTROL
1604 Capability: KVM_CAP_GET_TSC_KHZ
1617 Capability: KVM_CAP_IRQCHIP
1645 Capability: KVM_CAP_IRQCHIP
1660 regs field) depends on the state of the KVM_CAP_X2APIC_API capability.
1666 Capability: KVM_CAP_IOEVENTFD
1709 Capability: KVM_CAP_SW_TLB
1742 Capability: KVM_CAP_SPAPR_TCE
1751 and provides a scatter/gather capability for PAPR virtual I/O.
1778 Capability: KVM_CAP_PPC_RMA
1803 The KVM_CAP_PPC_RMA capability is 1 or 2 if the KVM_ALLOCATE_RMA ioctl
1811 Capability: KVM_CAP_USER_NMI
1837 Capability: KVM_CAP_S390_UCONTROL
1857 Capability: KVM_CAP_S390_UCONTROL
1877 Capability: KVM_CAP_S390_UCONTROL
1894 Capability: KVM_CAP_ONE_REG
2287 Capability: KVM_CAP_ONE_REG
2310 Capability: KVM_CAP_KVMCLOCK_CTRL
2331 Capability: KVM_CAP_SIGNAL_MSI
2350 KVM_CAP_MSI_DEVID capability advertises the requirement to provide
2351 the device ID. If this capability is not available, userspace
2359 feature of KVM_CAP_X2APIC_API capability is enabled. If it is enabled,
2366 Capability: KVM_CAP_PIT2
2398 Capability: KVM_CAP_PIT_STATE2
2423 Capability: KVM_CAP_PIT_STATE2
2437 Capability: KVM_CAP_PPC_GET_SMMU_INFO
2511 Capability: KVM_CAP_IRQFD
2548 Capability: KVM_CAP_PPC_ALLOC_HTAB
2557 virtualization. Otherwise the capability doesn't exist and the ioctl
2584 Capability: basic
2627 Capability: KVM_CAP_PPC_HTAB_FD
2681 Capability: KVM_CAP_DEVICE_CTRL
2712 Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device,
2740 Capability: KVM_CAP_DEVICE_CTRL, KVM_CAP_VM_ATTRIBUTES for vm device,
2756 Capability: basic
2836 Capability: basic
2860 Capability: basic
2880 Capability: KVM_CAP_ARM_SET_DEVICE_ADDR
2922 Capability: KVM_CAP_PPC_RTAS
2941 Capability: KVM_CAP_SET_GUEST_DEBUG
2991 Capability: KVM_CAP_EXT_EMUL_CPUID
3061 Capability: KVM_CAP_S390_MEM_OP
3097 KVM_CAP_S390_MEM_OP capability. "buf" is the buffer supplied by the
3109 Capability: KVM_CAP_S390_SKEYS
3140 Capability: KVM_CAP_S390_SKEYS
3167 Capability: KVM_CAP_S390_INJECT_IRQ
3221 Capability: KVM_CAP_S390_IRQ_STATE
3255 Capability: KVM_CAP_S390_IRQ_STATE
3292 Capability: KVM_CAP_X86_SMM
3302 Capability: KVM_CAP_PPC_MULTITCE
3306 This capability means the kernel is capable of handling hypercalls
3323 This capability is always enabled.
3327 Capability: KVM_CAP_SPAPR_TCE_64
3336 This capability uses extended struct in ioctl interface:
3359 Capability: KVM_CAP_REINJECT_CONTROL
3383 Capability: KVM_CAP_PPC_RADIX_MMU or KVM_CAP_PPC_HASH_MMU_V3
3414 Capability: KVM_CAP_PPC_RADIX_MMU
3448 Capability: KVM_CAP_SPAPR_RESIZE_HPT
3501 Capability: KVM_CAP_SPAPR_RESIZE_HPT
3543 Capability: KVM_CAP_MCE
3555 Capability: KVM_CAP_MCE
3562 -EINVAL if requested MCE capability is not supported.
3573 Capability: KVM_CAP_MCE
3606 Capability: KVM_CAP_S390_CMMA_MIGRATION
3696 Capability: KVM_CAP_S390_CMMA_MIGRATION
3741 Capability: KVM_CAP_PPC_GET_CPU_CHAR
3787 Capability: basic
3803 Capability: basic
3826 Capability: basic
3837 Capability: KVM_CAP_HYPERV_EVENTFD
3869 Capability: KVM_CAP_NESTED_STATE
3931 Capability: KVM_CAP_NESTED_STATE
3942 Capability: KVM_CAP_COALESCED_MMIO (for coalesced mmio)
3970 Capability: KVM_CAP_MANUAL_DIRTY_LOG_PROTECT2
4001 the KVM_CAP_MULTI_ADDRESS_SPACE capability.
4004 is enabled; for more information, see the description of the capability.
4010 Capability: KVM_CAP_HYPERV_CPUID
4101 Capability: KVM_CAP_PMU_EVENT_FILTER
4518 Target: whether this is a per-vcpu or per-vm capability.
4520 Parameters: what parameters are accepted by the capability.
4533 This capability enables interception of OSI hypercalls that otherwise would
4538 When this capability is enabled, KVM_EXIT_OSI can occur.
4548 This capability enables interception of PAPR hypercalls. PAPR hypercalls are
4558 When this capability is enabled, KVM_EXIT_PAPR_HCALL can occur.
4611 This capability enables support for handling of channel I/O instructions.
4616 When this capability is enabled, KVM_EXIT_S390_TSCH will occur on TEST
4619 Note that even though this capability is enabled per-vcpu, the complete
4629 This capability enables or disables the delivery of interrupts through the
4638 When this capability is enabled, KVM_EXIT_EPR can occur.
4646 This capability connects the vcpu to an in-kernel MPIC device.
4655 This capability connects the vcpu to an in-kernel XICS device.
4663 This capability enables the in-kernel irqchip for s390. Please refer to
4672 This capability allows the use of the host Floating Point Unit by the guest. It
4685 This capability allows the use of the MIPS SIMD Architecture (MSA) by the guest.
4738 This capability connects the vcpu to an in-kernel XIVE device.
4753 Parameters: what parameters are accepted by the capability.
4765 This capability controls whether individual sPAPR hypercalls (hcalls)
4770 before this capability was implemented. If disabled, the kernel will
4785 This capability controls which SIGP orders will be handled completely in user
4786 space. With this capability enabled, all fast orders will be handled completely
4797 in the hardware prior to interception). If this capability is not enabled, the
4815 This capability allows post-handlers for the STSI instruction. After
4849 This capability also enables in kernel routing of interrupt requests;
4894 With this capability enabled, all illegal instructions 0x0000 (2 bytes) will
4900 This capability can be enabled dynamically even if VCPUs were already
4925 Enabling this capability on a VM provides userspace with a way to set
4930 be 0. A successful call to enable this capability will result in
4931 vsmt_mode being returned when the KVM_CAP_PPC_SMT capability is
4932 subsequently queried for the VM. This capability is only supported by
4934 The KVM_CAP_PPC_SMT_POSSIBLE capability indicates which virtual SMT
4942 With this capability a machine check exception in the guest address
4945 machine check handling routine. Without this capability KVM will
4961 Enabling this capability on a VM provides userspace with a way to no
4978 With this capability the KVM support for memory backing with 1m pages
4979 through hugetlbfs can be enabled for a VM. After the capability is
4985 this capability, the VM will not be able to run.
4992 With this capability, a guest may read the MSR_PLATFORM_INFO MSR. Otherwise,
4994 capability does not enable write permissions of this MSR for the guest.
5006 state). Enabling this capability on a VM depends on the CPU having
5015 With this capability enabled, CR2 will not be modified prior to the
5027 This capability also enables exception.pending in struct
5040 With this capability enabled, KVM_GET_DIRTY_LOG will not automatically
5074 This capability, if KVM_CHECK_EXTENSION indicates that it is
5078 with the KVM_CAP_PPC_ENABLE_HCALL capability.
5083 This capability, if KVM_CHECK_EXTENSION indicates that it is
5089 capability via KVM_ENABLE_CAP ioctl on the vcpu fd. Note that this
5097 This capability, if KVM_CHECK_EXTENSION indicates that it is
5106 This capability, if KVM_CHECK_EXTENSION indicates that it is
5115 This capability, if KVM_CHECK_EXTENSION on the main kvm handle indicates that
5121 If KVM_CHECK_EXTENSION on a kvm VM handle indicates that this capability is
5142 This capability, if KVM_CHECK_EXTENSION on the main kvm handle indicates that
5148 If KVM_CHECK_EXTENSION on a kvm VM handle indicates that this capability is
5155 This capability indicates the supported architecture type of the guest, i.e. the
5158 The values returned when this capability is checked by KVM_CHECK_EXTENSION on a
5179 This capability, if KVM_CHECK_EXTENSION indicates that it is available, means
5202 number larger than 0 indicating the version of this capability is implemented
5221 Querying this capability returns a bitmap indicating the possible
5230 This capability enables a newer version of Hyper-V Synthetic interrupt
5239 This capability indicates that userspace can load HV_X64_MSR_VP_INDEX msr. Its
5242 capability is absent, userspace can still query this msr's value.
5249 This capability indicates if the flic device will be able to get/set the
5257 This capability indicates that the PSW is exposed via the kvm_run structure.
5263 This capability indicates that the user space memory used as guest mapping can
5271 This capability indicates that the user space memory used as guest mapping can
5279 This capability indicates that kvm will implement the interfaces to handle
5281 facility 82 should not be provided to the guest without this capability.
5287 This capability indicates that KVM supports paravirtualized Hyper-V TLB Flush
5296 This capability indicates that userspace can specify (via the
5299 If KVM advertises this capability, userspace can only specify the ISS field for
5309 This capability indicates that KVM supports paravirtualized Hyper-V IPI send
5316 This capability indicates that KVM running on top of Hyper-V hypervisor
5320 KVM, enabling this capability effectively disables all hypercall